AW: Load increase after memory upgrade?

All of lore.kernel.org
 help / color / mirror / Atom feed

* AW: Load increase after memory upgrade?
@ 2011-06-27 11:29 Carsten Schiers
  2011-06-27 13:46 ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 17+ messages in thread
From: Carsten Schiers @ 2011-06-27 11:29 UTC (permalink / raw)
  To: xen-devel, Konrad Rzeszutek Wilk

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

Hi,

the higher load is neither bound to memory increase nor Xen version, it's the kernel. 
Changed at the same time from a Xenified 2.6.34.7 kernel to pvops jeremy's git
stable-2.6.32.x

Konrad, are you interested? You can see from attached graphic the much higer load
mid 21 to 24. riker (yellow) is using the cards constantly for scanning transponders,
two seem to make use of DMA for that reason...

Carsten.

----- Originalnachricht -----
Von: Carsten Schiers <carsten@schiers.de>
Gesendet: Don, 23.6.2011 16:22
An: xen-devel <xen-devel@lists.xensource.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Betreff: Load increase after memory upgrade?

Hi,

after my memory upgrade 4GB -> 8GB, I noticed a much higher load in the Video DomU, 
related to some PCI cards that do DMA. I could check that it's related to two of the
three cards that use the same hardware architecture (budget_av and budget_ci) whereas
the b2c2_flexcop doesn't show shuch a behaviour.

As I changed at the same time from Xen 4.1.0 to 4.1.1, I wondered whether this is

  a) normal or pathologic
  b) related to Xen or the memory upgrade

Any thoughts? Can be seen as the yellow domain in my munin graphs.

Carsten.

[-- Attachment #2: xen_new-week.png --]
[-- Type: image/png, Size: 27542 bytes --]

[-- 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] 17+ messages in thread

* Re: AW: Load increase after memory upgrade?
  2011-06-27 11:29 AW: Load increase after memory upgrade? Carsten Schiers
@ 2011-06-27 13:46 ` Konrad Rzeszutek Wilk
  2011-06-27 15:37   ` Sander Eikelenboom
  2011-06-27 19:56   ` Carsten Schiers
  0 siblings, 2 replies; 17+ messages in thread
From: Konrad Rzeszutek Wilk @ 2011-06-27 13:46 UTC (permalink / raw)
  To: Carsten Schiers; +Cc: xen-devel

On Mon, Jun 27, 2011 at 01:29:24PM +0200, Carsten Schiers wrote:
> Hi,
> 
> the higher load is neither bound to memory increase nor Xen version, it's the kernel. 
> Changed at the same time from a Xenified 2.6.34.7 kernel to pvops jeremy's git
> stable-2.6.32.x
> 
> Konrad, are you interested? You can see from attached graphic the much higer load
> mid 21 to 24. riker (yellow) is using the cards constantly for scanning transponders,
> two seem to make use of DMA for that reason...

Um, so 2.6.34 to 2.6.32 causes this spike in usage? What is the SWIOTLB (PCI-DMA32)
usage between these two kernels and are the drivers (budget_...) the same version?

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

* Re: AW: Load increase after memory upgrade?
  2011-06-27 13:46 ` Konrad Rzeszutek Wilk
@ 2011-06-27 15:37   ` Sander Eikelenboom
  2011-06-27 20:00     ` AW: " Carsten Schiers
  2011-06-28 20:34     ` AW: " Carsten Schiers
  2011-06-27 19:56   ` Carsten Schiers
  1 sibling, 2 replies; 17+ messages in thread
From: Sander Eikelenboom @ 2011-06-27 15:37 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk; +Cc: xen-devel, Carsten Schiers

Hello Konrad,

Monday, June 27, 2011, 3:46:43 PM, you wrote:

> On Mon, Jun 27, 2011 at 01:29:24PM +0200, Carsten Schiers wrote:
>> Hi,
>> 
>> the higher load is neither bound to memory increase nor Xen version, it's the kernel. 
>> Changed at the same time from a Xenified 2.6.34.7 kernel to pvops jeremy's git
>> stable-2.6.32.x
>> 
>> Konrad, are you interested? You can see from attached graphic the much higer load
>> mid 21 to 24. riker (yellow) is using the cards constantly for scanning transponders,
>> two seem to make use of DMA for that reason...

> Um, so 2.6.34 to 2.6.32 causes this spike in usage? What is the SWIOTLB (PCI-DMA32)
> usage between these two kernels and are the drivers (budget_...) the same version?

is it actually the drivers that are consuming more cpu ?
2.6.32.x series still seem to show higher cpu utilazation and more wake-ups due to some console issue resulting in high events/0 in dom0.
That seems to be over in the new linux 3.0 kernels

--
Sander

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

* AW: Re: AW: Load increase after memory upgrade?
  2011-06-27 15:37   ` Sander Eikelenboom
@ 2011-06-27 20:00     ` Carsten Schiers
  2011-06-27 20:20       ` Sander Eikelenboom
  2011-06-28 14:50       ` Konrad Rzeszutek Wilk
  2011-06-28 20:34     ` AW: " Carsten Schiers
  1 sibling, 2 replies; 17+ messages in thread
From: Carsten Schiers @ 2011-06-27 20:00 UTC (permalink / raw)
  To: konrad.wilk, linux; +Cc: xen-devel

>That seems to be over in the new linux 3.0 kernels

If you recomend a kernel, I can try. Is jeremy's xen/next-3.0 capable to 
to pci-passthrough?

Carsten.

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

* Re: AW: Re: AW: Load increase after memory upgrade?
  2011-06-27 20:00     ` AW: " Carsten Schiers
@ 2011-06-27 20:20       ` Sander Eikelenboom
  2011-06-27 20:44         ` AW: " Carsten Schiers
  2011-06-27 20:46         ` Carsten Schiers
  2011-06-28 14:50       ` Konrad Rzeszutek Wilk
  1 sibling, 2 replies; 17+ messages in thread
From: Sander Eikelenboom @ 2011-06-27 20:20 UTC (permalink / raw)
  To: Carsten Schiers; +Cc: xen-devel, konrad.wilk



Monday, June 27, 2011, 10:00:43 PM, you wrote:

>>That seems to be over in the new linux 3.0 kernels

> If you recomend a kernel, I can try. Is jeremy's xen/next-3.0 capable to 
> to pci-passthrough?

I'm running konrad's master tree(git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git) with a additional patch that's the last one in his "devel/xen-pciback-0.6.1" tree (xen/pciback: revert the name of the PCI driver to ...).
The patch is necessary, otherwise the xen toolstack doesn't see the devices being owned by pciback.


> Carsten.




-- 
Best regards,
 Sander                            mailto:linux@eikelenboom.it

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

* AW: Re: AW: Re: AW: Load increase after memory upgrade?
  2011-06-27 20:20       ` Sander Eikelenboom
@ 2011-06-27 20:44         ` Carsten Schiers
  2011-06-27 20:46         ` Carsten Schiers
  1 sibling, 0 replies; 17+ messages in thread
From: Carsten Schiers @ 2011-06-27 20:44 UTC (permalink / raw)
  To: linux; +Cc: xen-devel, konrad.wilk

>I'm running konrad's master 
tree(git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git) with 
a additional patch that's the last one in his "devel/xen-pciback-0.6.1" 
tree >(xen/pciback: revert the name of the PCI driver to ...).
>The patch is necessary, otherwise the xen toolstack doesn't see the 
devices being owned by pciback.

Checking tomorrow. It seems the patch you mention is now already in (2 
hours ago) ;o).

Carsten.

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

* AW: Re: AW: Re: AW: Load increase after memory upgrade?
  2011-06-27 20:20       ` Sander Eikelenboom
  2011-06-27 20:44         ` AW: " Carsten Schiers
@ 2011-06-27 20:46         ` Carsten Schiers
  2011-06-28 14:57           ` Konrad Rzeszutek Wilk
  1 sibling, 1 reply; 17+ messages in thread
From: Carsten Schiers @ 2011-06-27 20:46 UTC (permalink / raw)
  To: linux; +Cc: xen-devel, konrad.wilk

>I'm running konrad's master 
tree(git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git) with 
a additional patch that's the last one in his "devel/xen-pciback-0.6.1" 
tree >(xen/pciback: revert the name of the PCI driver to ...).
>The patch is necessary, otherwise the xen toolstack doesn't see the 
devices being owned by pciback.

Forget what I just mailed. It's a head. I am not very used to all these 
git thingies...

Is there an easy way to describe the steps to do after

  git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git

?

Carsten.

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

* Re: Re: AW: Re: AW: Load increase after memory upgrade?
  2011-06-27 20:46         ` Carsten Schiers
@ 2011-06-28 14:57           ` Konrad Rzeszutek Wilk
  2011-06-28 20:17             ` AW: " Carsten Schiers
  2011-06-28 20:22             ` Carsten Schiers
  0 siblings, 2 replies; 17+ messages in thread
From: Konrad Rzeszutek Wilk @ 2011-06-28 14:57 UTC (permalink / raw)
  To: Carsten Schiers; +Cc: linux, xen-devel

On Mon, Jun 27, 2011 at 10:46:15PM +0200, Carsten Schiers wrote:
> >I'm running konrad's master 
> tree(git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git) with 
> a additional patch that's the last one in his "devel/xen-pciback-0.6.1" 
> tree >(xen/pciback: revert the name of the PCI driver to ...).
> >The patch is necessary, otherwise the xen toolstack doesn't see the 
> devices being owned by pciback.
> 
> Forget what I just mailed. It's a head. I am not very used to all these 
> git thingies...
> 
> Is there an easy way to describe the steps to do after
> 
>   git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git

Um, well, lets take one thing at a time.

a). What is the version of Dom0? Are you swapping that out? If so, and you
want the latests then the next step is to do:

cd xen
git merge origin/devel/xen-pciback-0.6.1
make

b). If you just want to use the later version of a kernel for DomU, you don't
need the xen pciback. You need the xen pcifront - which has some bug-fixes in 2.6.39.
So you can:

cd xen
git checkout v2.6.39
make

c). If you want to see if the fault here lies in the bounce buffer being used more
often in the DomU b/c you have 8GB of memory now and you end up using more pages
past 4GB (in DomU), I can cook up a patch to figure this out. But an easier way is
to just do (on the Xen hypervisor line): mem=4G and that will make think you only have
4GB of physical RAM.  If the load comes back to the normal "amount" then the likely
culprit is that and we can think on how to fix this.

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

* AW: Re: Re: AW: Re: AW: Load increase after memory upgrade?
  2011-06-28 14:57           ` Konrad Rzeszutek Wilk
@ 2011-06-28 20:17             ` Carsten Schiers
  2011-06-28 20:22             ` Carsten Schiers
  1 sibling, 0 replies; 17+ messages in thread
From: Carsten Schiers @ 2011-06-28 20:17 UTC (permalink / raw)
  To: konrad.wilk; +Cc: linux, xen-devel

>b). If you just want to use the later version of a kernel for DomU, you 
don't
>need the xen pciback. You need the xen pcifront - which has some 
bug-fixes in 2.6.39.

I started with this one. First observation: seems to generate high load 
(~20% in xentop, as opposed
to ~10% with the Xenified kernel).

Xen 4.1.1 with stable/2.6.39.x from Konrad xen.git.

Also a WARNING came up during boot, but everything works. But I thought 
you would eventually be able to 
read something from it:

[    2.850254] WARNING: at kernel/irq/handle.c:130 
handle_irq_event_percpu+0xa0/0x15f()
[    2.850274] irq 28 handler interrupt_hw+0x0/0x1b7 [saa7146] enabled 
interrupts
[    2.850288] Modules linked in: budget_ci(+) b2c2_flexcop(+) 
ir_rc5_decoder budget_core dvb_core ir_nec_decoder snd_pcm cx24123 
saa7146 snd_timer cx24113 snd ttpci_eeprom s5h1420 soundcore rc_core 
snd_page_alloc i2c_core pcspkr ext3 jbd mbcache xen_netfront 
xen_blkfront
[    2.850374] Pid: 141, comm: udevd Not tainted 2.6.39.2-xen-686 #4
[    2.850384] Call Trace:
[    2.850398]  [<c10361e8>] ? warn_slowpath_common+0x6a/0x7b
[    2.850411]  [<c107536b>] ? handle_irq_event_percpu+0xa0/0x15f
[    2.850424]  [<c103625f>] ? warn_slowpath_fmt+0x28/0x2c
[    2.850437]  [<c107536b>] ? handle_irq_event_percpu+0xa0/0x15f
[    2.850451]  [<d51cfe32>] ? SAA7146_IER_DISABLE+0x36/0x36 [saa7146]
[    2.850465]  [<c107544b>] ? handle_irq_event+0x21/0x37
[    2.850478]  [<c1076d36>] ? handle_fasteoi_irq+0x66/0x7e
[    2.850492]  [<c11a8515>] ? __xen_evtchn_do_upcall+0x129/0x1b0
[    2.850506]  [<c11a913b>] ? xen_evtchn_do_upcall+0x18/0x26
[    2.850519]  [<c12aea97>] ? xen_do_upcall+0x7/0xc
[    2.850532]  [<c114b407>] ? strcmp+0x8/0x19
[    2.850545]  [<c1104287>] ? sysfs_dentry_revalidate+0x38/0x88
[    2.850559]  [<c10ca1d1>] ? walk_component+0x18c/0x2b4
[    2.850571]  [<c1103437>] ? sysfs_permission+0x49/0x4f
[    2.850583]  [<c10ca96a>] ? link_path_walk+0x14f/0x38a
[    2.850597]  [<c1113e66>] ? security_file_alloc+0xc/0xd
[    2.850610]  [<c10cb9db>] ? path_openat+0x7f/0x27d
[    2.850623]  [<c10cbc7d>] ? do_filp_open+0x21/0x60
[    2.850635]  [<c10bdc68>] ? kmem_cache_alloc+0x21/0xd9
[    2.850647]  [<c10c921e>] ? getname_flags+0x20/0xbd
[    2.850660]  [<c10c04f4>] ? do_sys_open+0x58/0xd1
[    2.850672]  [<c10c05b1>] ? sys_open+0x1e/0x23
[    2.850684]  [<c12a901c>] ? syscall_call+0x7/0xb
[    2.850694] ---[ end trace 5b96651124c9fbda ]---

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

* AW: Re: Re: AW: Re: AW: Load increase after memory upgrade?
  2011-06-28 14:57           ` Konrad Rzeszutek Wilk
  2011-06-28 20:17             ` AW: " Carsten Schiers
@ 2011-06-28 20:22             ` Carsten Schiers
  2011-06-28 20:34               ` Konrad Rzeszutek Wilk
  1 sibling, 1 reply; 17+ messages in thread
From: Carsten Schiers @ 2011-06-28 20:22 UTC (permalink / raw)
  To: konrad.wilk; +Cc: linux, xen-devel

>a). What is the version of Dom0? Are you swapping that out? If so, and 
you
>want the latests then the next step is to do:

Dom0 is jeremy's git xen/stable-2.6.32.x in 64 Bit. DomUs are 32 Bit. 
Shall I 
experimently change that to what you recommended?


>c). If you want to see if the fault here lies in the bounce buffer 
being used more
>often in the DomU b/c you have 8GB of memory now and you end up using 
more pages
>past 4GB (in DomU), I can cook up a patch to figure this out. But an 
easier way is
>to just do (on the Xen hypervisor line): mem=4G and that will make 
think you only have
>4GB of physical RAM.  If the load comes back to the normal "amount" 
then the likely
>culprit is that and we can think on how to fix this.

So I will reboot with the a.m. parameter, but that's not possible right 
now. I 
will keep you informed. Eventually I can combine that with the test a) 
on Thursday.

Carsten.

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

* Re: Re: Re: AW: Re: AW: Load increase after memory upgrade?
  2011-06-28 20:22             ` Carsten Schiers
@ 2011-06-28 20:34               ` Konrad Rzeszutek Wilk
  2011-06-29 21:17                 ` AW: " Carsten Schiers
  0 siblings, 1 reply; 17+ messages in thread
From: Konrad Rzeszutek Wilk @ 2011-06-28 20:34 UTC (permalink / raw)
  To: Carsten Schiers; +Cc: linux, xen-devel

On Tue, Jun 28, 2011 at 10:22:34PM +0200, Carsten Schiers wrote:
> >a). What is the version of Dom0? Are you swapping that out? If so, and 
> you
> >want the latests then the next step is to do:
> 
> Dom0 is jeremy's git xen/stable-2.6.32.x in 64 Bit. DomUs are 32 Bit. 
> Shall I 
> experimently change that to what you recommended?

Lets first do the c) experiment as that will likely explain your load average increase.

> 
> 
> >c). If you want to see if the fault here lies in the bounce buffer 
> being used more
> >often in the DomU b/c you have 8GB of memory now and you end up using 
> more pages
> >past 4GB (in DomU), I can cook up a patch to figure this out. But an 
> easier way is
> >to just do (on the Xen hypervisor line): mem=4G and that will make 
> think you only have
> >4GB of physical RAM.  If the load comes back to the normal "amount" 
> then the likely
> >culprit is that and we can think on how to fix this.
> 
> So I will reboot with the a.m. parameter, but that's not possible right 
> now. I 
> will keep you informed. Eventually I can combine that with the test a) 
> on Thursday.
> 
> Carsten.

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

* AW: Re: Re: Re: AW: Re: AW: Load increase after memory upgrade?
  2011-06-28 20:34               ` Konrad Rzeszutek Wilk
@ 2011-06-29 21:17                 ` Carsten Schiers
  2011-06-30 22:00                   ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 17+ messages in thread
From: Carsten Schiers @ 2011-06-29 21:17 UTC (permalink / raw)
  To: konrad.wilk; +Cc: linux, xen-devel

> Lets first do the c) experiment as that will likely explain your load 
average increase.
...
> >c). If you want to see if the fault here lies in the bounce buffer 
> being used more
> >often in the DomU b/c you have 8GB of memory now and you end up using 

> more pages
> >past 4GB (in DomU), I can cook up a patch to figure this out. But an 
> easier way is
> >to just do (on the Xen hypervisor line): mem=4G and that will make 
> think you only have
> >4GB of physical RAM.  If the load comes back to the normal "amount" 
> then the likely
> >culprit is that and we can think on how to fix this.

You are on the right track. Load was going down to "normal" 10% when 
reducing
Xen to 4GB by the parameter. Load seems to be still a little, little bit 
lower
with Xenified Kernel (8-9%), but this is drastically lower than the 20% 
we had
before.

What to do next, Konrad?

Carsten.

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

* Re: Re: Re: Re: AW: Re: AW: Load increase after memory upgrade?
  2011-06-29 21:17                 ` AW: " Carsten Schiers
@ 2011-06-30 22:00                   ` Konrad Rzeszutek Wilk
  0 siblings, 0 replies; 17+ messages in thread
From: Konrad Rzeszutek Wilk @ 2011-06-30 22:00 UTC (permalink / raw)
  To: Carsten Schiers; +Cc: linux, xen-devel

On Wed, Jun 29, 2011 at 11:17:53PM +0200, Carsten Schiers wrote:
> > Lets first do the c) experiment as that will likely explain your load 
> average increase.
> ...
> > >c). If you want to see if the fault here lies in the bounce buffer 
> > being used more
> > >often in the DomU b/c you have 8GB of memory now and you end up using 
> 
> > more pages
> > >past 4GB (in DomU), I can cook up a patch to figure this out. But an 
> > easier way is
> > >to just do (on the Xen hypervisor line): mem=4G and that will make 
> > think you only have
> > >4GB of physical RAM.  If the load comes back to the normal "amount" 
> > then the likely
> > >culprit is that and we can think on how to fix this.
> 
> You are on the right track. Load was going down to "normal" 10% when 
> reducing
> Xen to 4GB by the parameter. Load seems to be still a little, little bit 
> lower
> with Xenified Kernel (8-9%), but this is drastically lower than the 20% 
> we had
> before.
> 
> What to do next, Konrad?

Yikes. I was hoping that was not the problem but it seems so. The issue is
here (I think) is that the PCI device you have passed in, are 32-bit.
Meaning they can only address memory up to 4GB. You should see if this
is the case - if the device is a PCI card, it definitly can only do 32-bit.

If it is PCIe, then it might be that the driver has set the DMA mask
to be only up to 32-bit.

Back to the explanation ..So if your guest (or the guest application) is
entirely above the 4GB region any of DMA operations have to be "bounced"
(or copied) to a region below 4GB. When the DMA operation is complete the
result is copied from below the 4GB back to the region above 8Gb.

Some drivers use the 'dma_alloc_coherent' which ends up allocating a
buffer that is below 4GB and use that all the time as to avoid the
bouncing. Mostly the IDE, SCSI and NICs do it.

One way that immediately comes in my mind to "fix" this is to force
the guest to be allocated from memory below 4GB. But not sure what
fancy parameters need to be turned on for this.

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

* Re: Re: AW: Load increase after memory upgrade?
  2011-06-27 20:00     ` AW: " Carsten Schiers
  2011-06-27 20:20       ` Sander Eikelenboom
@ 2011-06-28 14:50       ` Konrad Rzeszutek Wilk
  1 sibling, 0 replies; 17+ messages in thread
From: Konrad Rzeszutek Wilk @ 2011-06-28 14:50 UTC (permalink / raw)
  To: Carsten Schiers; +Cc: linux, xen-devel

On Mon, Jun 27, 2011 at 10:00:43PM +0200, Carsten Schiers wrote:
> >That seems to be over in the new linux 3.0 kernels
> 
> If you recomend a kernel, I can try. Is jeremy's xen/next-3.0 capable to 
> to pci-passthrough?

Any 2.6.37 or later kernel has the PCI passthrough frontend driver in it.
> 
> Carsten.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

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

* AW: Re: AW: Load increase after memory upgrade?
  2011-06-27 15:37   ` Sander Eikelenboom
  2011-06-27 20:00     ` AW: " Carsten Schiers
@ 2011-06-28 20:34     ` Carsten Schiers
  1 sibling, 0 replies; 17+ messages in thread
From: Carsten Schiers @ 2011-06-28 20:34 UTC (permalink / raw)
  To: konrad.wilk, linux; +Cc: xen-devel

>is it actually the drivers that are consuming more cpu ?
>2.6.32.x series still seem to show higher cpu utilazation and more 
wake-ups due to some console issue resulting in high events/0 in dom0.
>That seems to be over in the new linux 3.0 kernels

It seems that with the lower cpu utilization, main reasons to wake up 
according to powertop are:

  1) timer (~50%)
  2) saa7146(0)
  3) saa7146(1)

Whereas with higher CPU utilization its:

  1) flexcop-pci
  2) saa7146(0)
  3) saa7146(1)
  4) timer (<10%)

If that helps. Funny: taking out the flexcop card will not change load, 
but taking out the saa7146 cards will lower load on the other kernel 
also.

Carsten.  

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

* AW: Re: AW: Load increase after memory upgrade?
  2011-06-27 13:46 ` Konrad Rzeszutek Wilk
  2011-06-27 15:37   ` Sander Eikelenboom
@ 2011-06-27 19:56   ` Carsten Schiers
  2011-06-28 14:49     ` Konrad Rzeszutek Wilk
  1 sibling, 1 reply; 17+ messages in thread
From: Carsten Schiers @ 2011-06-27 19:56 UTC (permalink / raw)
  To: konrad.wilk; +Cc: xen-devel

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

>Um, so 2.6.34 to 2.6.32 causes this spike in usage? 

Definitely yes. 

> What is the SWIOTLB (PCI-DMA32) usage between these two kernels 

I don't understand. What do you mean? The only difference is that I call 
up the swiotlb differently:

On pvops: iommu=soft
On rebased: swiotlb=32,force

BTW: changing to 64,force doesn't make a difference.

I attached a normal boot log of both kernels.

> and are the drivers (budget_...) the same version?

No, but a quick diff between the two source trees offer only minor 
changes that from the first look
do not seem to be related to DMA or whatever.

Carsten.



[-- Attachment #2: 41er --]
[-- Type: application/octet-stream, Size: 22862 bytes --]

Jun 22 10:12:08 riker kernel: [    0.000000] Reserving virtual address space above 0xf5800000
Jun 22 10:12:08 riker kernel: [    0.000000] Initializing cgroup subsys cpuset
Jun 22 10:12:08 riker kernel: [    0.000000] Initializing cgroup subsys cpu
Jun 22 10:12:08 riker kernel: [    0.000000] Linux version 2.6.32.41-xen-686 (root@spock) (gcc version 4.4.5 (Debian 4.4.5-8) ) #2 SMP Tue Jun 21 23:30:58 CEST 2011
Jun 22 10:12:08 riker kernel: [    0.000000] KERNEL supported cpus:
Jun 22 10:12:08 riker kernel: [    0.000000]   Intel GenuineIntel
Jun 22 10:12:08 riker kernel: [    0.000000]   AMD AuthenticAMD
Jun 22 10:12:08 riker kernel: [    0.000000]   NSC Geode by NSC
Jun 22 10:12:08 riker kernel: [    0.000000]   Cyrix CyrixInstead
Jun 22 10:12:08 riker kernel: [    0.000000]   Centaur CentaurHauls
Jun 22 10:12:08 riker kernel: [    0.000000]   Transmeta GenuineTMx86
Jun 22 10:12:08 riker kernel: [    0.000000]   Transmeta TransmetaCPU
Jun 22 10:12:08 riker kernel: [    0.000000]   UMC UMC UMC UMC
Jun 22 10:12:08 riker kernel: [    0.000000] ACPI in unprivileged domain disabled
Jun 22 10:12:08 riker kernel: [    0.000000] released 0 pages of unused memory
Jun 22 10:12:08 riker kernel: [    0.000000] BIOS-provided physical RAM map:
Jun 22 10:12:08 riker kernel: [    0.000000]  Xen: 0000000000000000 - 00000000000a0000 (usable)
Jun 22 10:12:08 riker kernel: [    0.000000]  Xen: 00000000000a0000 - 0000000000100000 (reserved)
Jun 22 10:12:08 riker kernel: [    0.000000]  Xen: 0000000000100000 - 0000000010800000 (usable)
Jun 22 10:12:08 riker kernel: [    0.000000] DMI not present or invalid.
Jun 22 10:12:08 riker kernel: [    0.000000] last_pfn = 0x10800 max_arch_pfn = 0x1000000
Jun 22 10:12:08 riker kernel: [    0.000000] init_memory_mapping: 0000000000000000-0000000010800000
Jun 22 10:12:08 riker kernel: [    0.000000] NX (Execute Disable) protection: active
Jun 22 10:12:08 riker kernel: [    0.000000] RAMDISK: 0166f000 - 02aa5000
Jun 22 10:12:08 riker kernel: [    0.000000] 0MB HIGHMEM available.
Jun 22 10:12:08 riker kernel: [    0.000000] 264MB LOWMEM available.
Jun 22 10:12:08 riker kernel: [    0.000000]   mapped low ram: 0 - 10800000
Jun 22 10:12:08 riker kernel: [    0.000000]   low ram: 0 - 10800000
Jun 22 10:12:08 riker kernel: [    0.000000]   node 0 low ram: 00000000 - 10800000
Jun 22 10:12:08 riker kernel: [    0.000000]   node 0 bootmap 00002000 - 00004100
Jun 22 10:12:08 riker kernel: [    0.000000] (11 early reservations) ==> bootmem [0000000000 - 0010800000]
Jun 22 10:12:08 riker kernel: [    0.000000]   #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
Jun 22 10:12:08 riker kernel: [    0.000000]   #1 [0002ae8000 - 0002b00000]   XEN PAGETABLES ==> [0002ae8000 - 0002b00000]
Jun 22 10:12:08 riker kernel: [    0.000000]   #2 [0000001000 - 0000002000]    EX TRAMPOLINE ==> [0000001000 - 0000002000]
Jun 22 10:12:08 riker kernel: [    0.000000]   #3 [0000006000 - 0000007000]       TRAMPOLINE ==> [0000006000 - 0000007000]
Jun 22 10:12:08 riker kernel: [    0.000000]   #4 [0001000000 - 00014fe8d4]    TEXT DATA BSS ==> [0001000000 - 00014fe8d4]
Jun 22 10:12:08 riker kernel: [    0.000000]   #5 [000166f000 - 0002aa5000]          RAMDISK ==> [000166f000 - 0002aa5000]
Jun 22 10:12:08 riker kernel: [    0.000000]   #6 [0002aa5000 - 0002ae8000]   XEN START INFO ==> [0002aa5000 - 0002ae8000]
Jun 22 10:12:08 riker kernel: [    0.000000]   #7 [0010000000 - 0010800000]        XEN EXTRA ==> [0010000000 - 0010800000]
Jun 22 10:12:08 riker kernel: [    0.000000]   #8 [00014ff000 - 000150c000]              BRK ==> [00014ff000 - 000150c000]
Jun 22 10:12:08 riker kernel: [    0.000000]   #9 [0000007000 - 0000074000]          PGTABLE ==> [0000007000 - 0000074000]
Jun 22 10:12:08 riker kernel: [    0.000000]   #10 [0000002000 - 0000005000]          BOOTMAP ==> [0000002000 - 0000005000]
Jun 22 10:12:08 riker kernel: [    0.000000] Zone PFN ranges:
Jun 22 10:12:08 riker kernel: [    0.000000]   DMA      0x00000000 -> 0x00001000
Jun 22 10:12:08 riker kernel: [    0.000000]   Normal   0x00001000 -> 0x00010800
Jun 22 10:12:08 riker kernel: [    0.000000]   HighMem  0x00010800 -> 0x00010800
Jun 22 10:12:08 riker kernel: [    0.000000] Movable zone start PFN for each node
Jun 22 10:12:08 riker kernel: [    0.000000] early_node_map[2] active PFN ranges
Jun 22 10:12:08 riker kernel: [    0.000000]     0: 0x00000000 -> 0x000000a0
Jun 22 10:12:08 riker kernel: [    0.000000]     0: 0x00000100 -> 0x00010800
Jun 22 10:12:08 riker kernel: [    0.000000] Using APIC driver default
Jun 22 10:12:08 riker kernel: [    0.000000] SFI: Simple Firmware Interface v0.7 http://simplefirmware.org
Jun 22 10:12:08 riker kernel: [    0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs
Jun 22 10:12:08 riker kernel: [    0.000000] Local APIC disabled by BIOS -- you can enable it with "lapic"
Jun 22 10:12:08 riker kernel: [    0.000000] APIC: disable apic facility
Jun 22 10:12:08 riker kernel: [    0.000000] PM: Registered nosave memory: 00000000000a0000 - 0000000000100000
Jun 22 10:12:08 riker kernel: [    0.000000] Allocating PCI resources starting at 10800000 (gap: 10800000:ef800000)
Jun 22 10:12:08 riker kernel: [    0.000000] Booting paravirtualized kernel on Xen
Jun 22 10:12:08 riker kernel: [    0.000000] Xen version: 4.1.1 (preserve-AD)
Jun 22 10:12:08 riker kernel: [    0.000000] NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:1 nr_node_ids:1
Jun 22 10:12:08 riker kernel: [    0.000000] PERCPU: Embedded 15 pages/cpu @c2d13000 s37720 r0 d23720 u65536
Jun 22 10:12:08 riker kernel: [    0.000000] pcpu-alloc: s37720 r0 d23720 u65536 alloc=16*4096
Jun 22 10:12:08 riker kernel: [    0.000000] pcpu-alloc: [0] 0 
Jun 22 10:12:08 riker kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 66960
Jun 22 10:12:08 riker kernel: [    0.000000] Kernel command line: root=/dev/xvda1 ro iommu=soft xencons=tty
Jun 22 10:12:08 riker kernel: [    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
Jun 22 10:12:08 riker kernel: [    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Jun 22 10:12:08 riker kernel: [    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Jun 22 10:12:08 riker kernel: [    0.000000] Enabling fast FPU save and restore... done.
Jun 22 10:12:08 riker kernel: [    0.000000] Enabling unmasked SIMD FPU exception support... done.
Jun 22 10:12:08 riker kernel: [    0.000000] Initializing CPU#0
Jun 22 10:12:08 riker kernel: [    0.000000] DMA: Placing 64MB software IO TLB between c2d85000 - c6d85000
Jun 22 10:12:08 riker kernel: [    0.000000] DMA: software IO TLB at phys 0x2d85000 - 0x6d85000
Jun 22 10:12:08 riker kernel: [    0.000000] xen_swiotlb_fixup: buf=c2d85000 size=67108864
Jun 22 10:12:08 riker kernel: [    0.000000] xen_swiotlb_fixup: buf=c6de5000 size=32768
Jun 22 10:12:08 riker kernel: [    0.000000] Initializing HighMem for node 0 (00000000:00000000)
Jun 22 10:12:08 riker kernel: [    0.000000] Memory: 166320k/270336k available (2591k kernel code, 103416k reserved, 1375k data, 404k init, 0k highmem)
Jun 22 10:12:08 riker kernel: [    0.000000] virtual kernel memory layout:
Jun 22 10:12:08 riker kernel: [    0.000000]     fixmap  : 0xf5556000 - 0xf57ff000   (2724 kB)
Jun 22 10:12:08 riker kernel: [    0.000000]     pkmap   : 0xf5000000 - 0xf5200000   (2048 kB)
Jun 22 10:12:08 riker kernel: [    0.000000]     vmalloc : 0xd1000000 - 0xf4ffe000   ( 575 MB)
Jun 22 10:12:08 riker kernel: [    0.000000]     lowmem  : 0xc0000000 - 0xd0800000   ( 264 MB)
Jun 22 10:12:08 riker kernel: [    0.000000]       .init : 0xc13e0000 - 0xc1445000   ( 404 kB)
Jun 22 10:12:08 riker kernel: [    0.000000]       .data : 0xc1287e85 - 0xc13dfb18   (1375 kB)
Jun 22 10:12:08 riker kernel: [    0.000000]       .text : 0xc1000000 - 0xc1287e85   (2591 kB)
Jun 22 10:12:08 riker kernel: [    0.000000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Jun 22 10:12:08 riker kernel: [    0.000000] Hierarchical RCU implementation.
Jun 22 10:12:08 riker kernel: [    0.000000] NR_IRQS:1536
Jun 22 10:12:08 riker kernel: [    0.000000] Console: colour dummy device 80x25
Jun 22 10:12:08 riker kernel: [    0.000000] console [tty0] enabled
Jun 22 10:12:08 riker kernel: [    0.000000] console [hvc0] enabled
Jun 22 10:12:08 riker kernel: [    0.000000] installing Xen timer for CPU 0
Jun 22 10:12:08 riker kernel: [    0.000000] Detected 2210.036 MHz processor.
Jun 22 10:12:08 riker kernel: [    0.004000] Calibrating delay loop (skipped), value calculated using timer frequency.. 4420.07 BogoMIPS (lpj=8840144)
Jun 22 10:12:08 riker kernel: [    0.004000] Security Framework initialized
Jun 22 10:12:08 riker kernel: [    0.004000] SELinux:  Disabled at boot.
Jun 22 10:12:08 riker kernel: [    0.004000] Mount-cache hash table entries: 512
Jun 22 10:12:08 riker kernel: [    0.004000] Initializing cgroup subsys ns
Jun 22 10:12:08 riker kernel: [    0.004000] Initializing cgroup subsys cpuacct
Jun 22 10:12:08 riker kernel: [    0.004000] Initializing cgroup subsys devices
Jun 22 10:12:08 riker kernel: [    0.004000] Initializing cgroup subsys freezer
Jun 22 10:12:08 riker kernel: [    0.004000] Initializing cgroup subsys net_cls
Jun 22 10:12:08 riker kernel: [    0.004000] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
Jun 22 10:12:08 riker kernel: [    0.004000] CPU: L2 Cache: 512K (64 bytes/line)
Jun 22 10:12:08 riker kernel: [    0.004000] CPU: Physical Processor ID: 0
Jun 22 10:12:08 riker kernel: [    0.004000] CPU: Processor Core ID: 0
Jun 22 10:12:08 riker kernel: [    0.004000] Performance Events: AMD PMU driver.
Jun 22 10:12:08 riker kernel: [    0.004000] ... version:                0
Jun 22 10:12:08 riker kernel: [    0.004000] ... bit width:              48
Jun 22 10:12:08 riker kernel: [    0.004000] ... generic registers:      4
Jun 22 10:12:08 riker kernel: [    0.004000] ... value mask:             0000ffffffffffff
Jun 22 10:12:08 riker kernel: [    0.004000] ... max period:             00007fffffffffff
Jun 22 10:12:08 riker kernel: [    0.004000] ... fixed-purpose events:   0
Jun 22 10:12:08 riker kernel: [    0.004000] ... event mask:             000000000000000f
Jun 22 10:12:08 riker kernel: [    0.004000] SMP alternatives: switching to UP code
Jun 22 10:12:08 riker kernel: [    0.004000] Freeing SMP alternatives: 13k freed
Jun 22 10:12:08 riker kernel: [    0.004266] Brought up 1 CPUs
Jun 22 10:12:08 riker kernel: [    0.004398] devtmpfs: initialized
Jun 22 10:12:08 riker kernel: [    0.004968] Grant table initialized
Jun 22 10:12:08 riker kernel: [    0.004977] regulator: core version 0.5
Jun 22 10:12:08 riker kernel: [    0.005040] NET: Registered protocol family 16
Jun 22 10:12:08 riker kernel: [    0.005224] PCI: setting up Xen PCI frontend stub
Jun 22 10:12:08 riker kernel: [    0.005224] bio: create slab <bio-0> at 0
Jun 22 10:12:08 riker kernel: [    0.005224] ACPI: Interpreter disabled.
Jun 22 10:12:08 riker kernel: [    0.008017] xen_balloon: Initialising balloon driver with page order 0.
Jun 22 10:12:08 riker kernel: [    0.008041] last_pfn = 0x10800 max_arch_pfn = 0x1000000
Jun 22 10:12:08 riker kernel: [    0.008076] vgaarb: loaded
Jun 22 10:12:08 riker kernel: [    0.008124] PCI: System does not support PCI
Jun 22 10:12:08 riker kernel: [    0.008130] PCI: System does not support PCI
Jun 22 10:12:08 riker kernel: [    0.008213] Switching to clocksource xen
Jun 22 10:12:08 riker kernel: [    0.009737] pnp: PnP ACPI: disabled
Jun 22 10:12:08 riker kernel: [    0.009751] PnPBIOS: Disabled
Jun 22 10:12:08 riker kernel: [    0.010003] NET: Registered protocol family 2
Jun 22 10:12:08 riker kernel: [    0.010093] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
Jun 22 10:12:08 riker kernel: [    0.010360] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
Jun 22 10:12:08 riker kernel: [    0.010433] TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
Jun 22 10:12:08 riker kernel: [    0.010501] TCP: Hash tables configured (established 16384 bind 16384)
Jun 22 10:12:08 riker kernel: [    0.010509] TCP reno registered
Jun 22 10:12:08 riker kernel: [    0.010578] NET: Registered protocol family 1
Jun 22 10:12:08 riker kernel: [    0.010640] Unpacking initramfs...
Jun 22 10:12:08 riker kernel: [    0.035250] Freeing initrd memory: 20696k freed
Jun 22 10:12:08 riker kernel: [    0.043065] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jun 22 10:12:08 riker kernel: [    0.043078] DMA: Placing 64MB software IO TLB between c2d85000 - c6d85000
Jun 22 10:12:08 riker kernel: [    0.043086] DMA: software IO TLB at phys 0x2d85000 - 0x6d85000
Jun 22 10:12:08 riker kernel: [    0.043155] platform rtc_cmos: registered platform RTC device (no PNP device found)
Jun 22 10:12:08 riker kernel: [    0.043337] audit: initializing netlink socket (disabled)
Jun 22 10:12:08 riker kernel: [    0.043354] type=2000 audit(1308730317.716:1): initialized
Jun 22 10:12:08 riker kernel: [    0.047963] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jun 22 10:12:08 riker kernel: [    0.049869] VFS: Disk quotas dquot_6.5.2
Jun 22 10:12:08 riker kernel: [    0.049928] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Jun 22 10:12:08 riker kernel: [    0.050016] msgmni has been set to 365
Jun 22 10:12:08 riker kernel: [    0.050220] alg: No test for stdrng (krng)
Jun 22 10:12:08 riker kernel: [    0.050278] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
Jun 22 10:12:08 riker kernel: [    0.050287] io scheduler noop registered
Jun 22 10:12:08 riker kernel: [    0.050292] io scheduler anticipatory registered
Jun 22 10:12:08 riker kernel: [    0.050298] io scheduler deadline registered
Jun 22 10:12:08 riker kernel: [    0.050338] io scheduler cfq registered (default)
Jun 22 10:12:08 riker kernel: [    0.059531] isapnp: ISA Plug & Play support disabled
Jun 22 10:12:08 riker kernel: [    0.064090] pcifront pci-0: Installing PCI frontend
Jun 22 10:12:08 riker kernel: [    0.064221] pcifront pci-0: Creating PCI Frontend Bus 0000:00
Jun 22 10:12:08 riker kernel: [    0.068060] pcifront pci-0: claiming resource 0000:00:00.0/0
Jun 22 10:12:08 riker kernel: [    0.068060] pcifront pci-0: claiming resource 0000:00:01.0/0
Jun 22 10:12:08 riker kernel: [    0.068060] pcifront pci-0: claiming resource 0000:00:02.0/0
Jun 22 10:12:08 riker kernel: [    0.068060] pcifront pci-0: claiming resource 0000:00:02.0/1
Jun 22 10:12:08 riker kernel: [    0.073152] Linux agpgart interface v0.103
Jun 22 10:12:08 riker kernel: [    0.073259] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
Jun 22 10:12:08 riker kernel: [    0.073490] PNP: No PS/2 controller found. Probing ports directly.
Jun 22 10:12:08 riker kernel: [    0.074354] mice: PS/2 mouse device common for all mice
Jun 22 10:12:08 riker kernel: [    0.074443] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
Jun 22 10:12:08 riker kernel: [    0.074504] cpuidle: using governor ladder
Jun 22 10:12:08 riker kernel: [    0.074510] cpuidle: using governor menu
Jun 22 10:12:08 riker kernel: [    0.074517] No iBFT detected.
Jun 22 10:12:08 riker kernel: [    0.074850] TCP cubic registered
Jun 22 10:12:08 riker kernel: [    0.167323] NET: Registered protocol family 10
Jun 22 10:12:08 riker kernel: [    0.168069] Mobile IPv6
Jun 22 10:12:08 riker kernel: [    0.168075] NET: Registered protocol family 17
Jun 22 10:12:08 riker kernel: [    0.168092] Using IPI No-Shortcut mode
Jun 22 10:12:08 riker kernel: [    0.168181] registered taskstats version 1
Jun 22 10:12:08 riker kernel: [    0.268124] XENBUS: Device with no driver: device/vbd/51713
Jun 22 10:12:08 riker kernel: [    0.268138] XENBUS: Device with no driver: device/vbd/51714
Jun 22 10:12:08 riker kernel: [    0.268144] XENBUS: Device with no driver: device/vbd/51729
Jun 22 10:12:08 riker kernel: [    0.268150] XENBUS: Device with no driver: device/vif/0
Jun 22 10:12:08 riker kernel: [    0.268156] XENBUS: Device with no driver: device/console/0
Jun 22 10:12:08 riker kernel: [    0.268184] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Jun 22 10:12:08 riker kernel: [    0.268212] Initalizing network drop monitor service
Jun 22 10:12:08 riker kernel: [    0.268274] Freeing unused kernel memory: 404k freed
Jun 22 10:12:08 riker kernel: [    0.269161] Write protecting the kernel text: 2592k
Jun 22 10:12:08 riker kernel: [    0.269450] Write protecting the kernel read-only data: 928k
Jun 22 10:12:08 riker kernel: [    0.304197] udev[47]: starting version 164
Jun 22 10:12:08 riker kernel: [    0.369552] Initialising Xen virtual ethernet driver.
Jun 22 10:12:08 riker kernel: [    0.472595] blkfront: xvda1: barriers enabled (tag)
Jun 22 10:12:08 riker kernel: [    0.500858] Setting capacity to 4194304
Jun 22 10:12:08 riker kernel: [    0.500879] xvda1: detected capacity change from 0 to 2147483648
Jun 22 10:12:08 riker kernel: [    0.508839] blkfront: xvda2: barriers enabled (tag)
Jun 22 10:12:08 riker kernel: [    0.524475] blkfront: xvdb1: barriers enabled (tag)
Jun 22 10:12:08 riker kernel: [    0.527557] Setting capacity to 2097152
Jun 22 10:12:08 riker kernel: [    0.527573] xvda2: detected capacity change from 0 to 1073741824
Jun 22 10:12:08 riker kernel: [    0.527991] Setting capacity to 2930272002
Jun 22 10:12:08 riker kernel: [    0.527999] xvdb1: detected capacity change from 0 to 1500299265024
Jun 22 10:12:08 riker kernel: [    0.876443] PM: Starting manual resume from disk
Jun 22 10:12:08 riker kernel: [    0.921374] kjournald starting.  Commit interval 5 seconds
Jun 22 10:12:08 riker kernel: [    0.921408] EXT3-fs: mounted filesystem with ordered data mode.
Jun 22 10:12:08 riker kernel: [    2.855633] udev[153]: starting version 164
Jun 22 10:12:08 riker kernel: [    3.546863] input: PC Speaker as /devices/platform/pcspkr/input/input0
Jun 22 10:12:08 riker kernel: [    4.130804] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully
Jun 22 10:12:08 riker kernel: [    4.156989] flexcop-pci: will use the HW PID filter.
Jun 22 10:12:08 riker kernel: [    4.157099] flexcop-pci: card revision 2
Jun 22 10:12:08 riker kernel: [    4.157397] b2c2_flexcop_pci 0000:00:02.0: Xen PCI enabling IRQ: 19
Jun 22 10:12:08 riker kernel: [    4.161481] saa7146: register extension 'budget_ci dvb'.
Jun 22 10:12:08 riker kernel: [    4.174436] DVB: registering new adapter (FlexCop Digital TV device)
Jun 22 10:12:08 riker kernel: [    4.177613] b2c2-flexcop: MAC address = 00:d0:d7:08:0c:bc
Jun 22 10:12:08 riker kernel: [    4.316285] Linux video capture interface: v2.00
Jun 22 10:12:08 riker kernel: [    4.457137] saa7146: register extension 'budget_av'.
Jun 22 10:12:08 riker kernel: [    4.652630] mt352_read_register: readreg error (reg=127, ret==-121)
Jun 22 10:12:08 riker kernel: [    4.666022] nxt200x: nxt200x_readbytes: i2c read error (addr 0x0a, err == -121)
Jun 22 10:12:08 riker kernel: [    4.666065] Unknown/Unsupported NXT chip: 00 00 00 00 00
Jun 22 10:12:08 riker kernel: [    4.692105] lgdt330x: i2c_read_demod_bytes: addr 0x59 select 0x02 error (ret == -121)
Jun 22 10:12:08 riker kernel: [    4.780674] b2c2-flexcop: found 'ST STV0297 DVB-C' .
Jun 22 10:12:08 riker kernel: [    4.780702] DVB: registering adapter 0 frontend 0 (ST STV0297 DVB-C)...
Jun 22 10:12:08 riker kernel: [    4.780804] b2c2-flexcop: initialization of 'Cable2PC/CableStar 2 DVB-C' at the 'PCI' bus controlled by a 'FlexCopIIb' complete
Jun 22 10:12:08 riker kernel: [    4.783305] budget_ci dvb 0000:00:01.0: Xen PCI enabling IRQ: 18
Jun 22 10:12:08 riker kernel: [    4.784225] IRQ 18/: IRQF_DISABLED is not guaranteed on shared IRQs
Jun 22 10:12:08 riker kernel: [    4.784344] saa7146: found saa7146 @ mem d149a000 (revision 1, irq 18) (0x13c2,0x1010).
Jun 22 10:12:08 riker kernel: [    4.784382] saa7146 (0): dma buffer size 1443840
Jun 22 10:12:08 riker kernel: [    4.784400] DVB: registering new adapter (TT-Budget-C-CI PCI)
Jun 22 10:12:08 riker kernel: [    4.791189] adapter has MAC addr = 00:d0:5c:67:c4:ab
Jun 22 10:12:08 riker kernel: [    4.794723] input: Budget-CI dvb ir receiver saa7146 (0) as /devices/pci-0/pci0000:00/0000:00:01.0/input/input1
Jun 22 10:12:08 riker kernel: [    4.795394] DVB: registering adapter 1 frontend 0 (ST STV0297 DVB-C)...
Jun 22 10:12:08 riker kernel: [    4.795758] budget_av 0000:00:00.0: Xen PCI enabling IRQ: 17
Jun 22 10:12:08 riker kernel: [    4.797688] IRQ 17/: IRQF_DISABLED is not guaranteed on shared IRQs
Jun 22 10:12:08 riker kernel: [    4.797813] saa7146: found saa7146 @ mem d1732000 (revision 1, irq 17) (0x1894,0x002c).
Jun 22 10:12:08 riker kernel: [    4.797849] saa7146 (1): dma buffer size 1347584
Jun 22 10:12:08 riker kernel: [    4.797865] DVB: registering new adapter (Satelco EasyWatch DVB-C MK3)
Jun 22 10:12:08 riker kernel: [    4.833123] adapter failed MAC signature check
Jun 22 10:12:08 riker kernel: [    4.833137] encoded MAC from EEPROM was ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff
Jun 22 10:12:08 riker kernel: [    5.096486] KNC1-2: MAC addr = 00:09:d6:6d:b0:33
Jun 22 10:12:08 riker kernel: [    5.237026] DVB: registering adapter 2 frontend 0 (Philips TDA10023 DVB-C)...
Jun 22 10:12:08 riker kernel: [    5.237303] budget-av: ci interface initialised.
Jun 22 10:12:08 riker kernel: [    6.191749] Adding 1048568k swap on /dev/xvda2.  Priority:-1 extents:1 across:1048568k SS
Jun 22 10:12:08 riker kernel: [    6.195587] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Jun 22 10:12:08 riker kernel: [    6.196116] EXT3 FS on xvda1, internal journal
Jun 22 10:12:08 riker kernel: [    6.736186] kjournald starting.  Commit interval 5 seconds
Jun 22 10:12:08 riker kernel: [    6.736212] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Jun 22 10:12:08 riker kernel: [    6.739717] EXT3 FS on xvdb1, internal journal
Jun 22 10:12:08 riker kernel: [    6.739735] EXT3-fs: mounted filesystem with ordered data mode.
Jun 22 10:12:08 riker kernel: [    8.879416] RPC: Registered udp transport module.
Jun 22 10:12:08 riker kernel: [    8.879431] RPC: Registered tcp transport module.
Jun 22 10:12:08 riker kernel: [    8.879438] RPC: Registered tcp NFSv4.1 backchannel transport module.
Jun 22 10:12:08 riker kernel: [    8.950712] Slow work thread pool: Starting up
Jun 22 10:12:08 riker kernel: [    8.950789] Slow work thread pool: Ready
Jun 22 10:12:08 riker kernel: [    8.950853] FS-Cache: Loaded
Jun 22 10:12:08 riker kernel: [    9.152374] FS-Cache: Netfs 'nfs' registered for caching
Jun 22 10:12:08 riker kernel: [    9.169109] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Jun 22 10:12:08 riker kernel: [   10.292307] svc: failed to register lockdv1 RPC service (errno 97).

[-- Attachment #3: xenfied --]
[-- Type: application/octet-stream, Size: 20046 bytes --]

May 22 15:22:23 riker kernel: [    0.000000] Linux version 2.6.34.7.1-xen-686 (root@spock) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #2 SMP Tue Nov 23 15:24:58 CET 2010
May 22 15:22:23 riker kernel: [    0.000000] Xen-provided physical RAM map:
May 22 15:22:23 riker kernel: [    0.000000]  Xen: 0000000000000000 - 0000000010800000 (usable)
May 22 15:22:23 riker kernel: [    0.000000] NX (Execute Disable) protection: active
May 22 15:22:23 riker kernel: [    0.000000] last_pfn = 0x10800 max_arch_pfn = 0x10000000
May 22 15:22:23 riker kernel: [    0.000000] init_memory_mapping: 0000000000000000-0000000010800000
May 22 15:22:23 riker kernel: [    0.000000] RAMDISK: 015c6000 - 0196f000
May 22 15:22:23 riker kernel: [    0.000000] 0MB HIGHMEM available.
May 22 15:22:23 riker kernel: [    0.000000] 264MB LOWMEM available.
May 22 15:22:23 riker kernel: [    0.000000]   mapped low ram: 0 - 10800000
May 22 15:22:23 riker kernel: [    0.000000]   low ram: 0 - 10800000
May 22 15:22:23 riker kernel: [    0.000000] Zone PFN ranges:
May 22 15:22:23 riker kernel: [    0.000000]   DMA      0x00000000 -> 0x00001000
May 22 15:22:23 riker kernel: [    0.000000]   Normal   0x00001000 -> 0x00010800
May 22 15:22:23 riker kernel: [    0.000000]   HighMem  empty
May 22 15:22:23 riker kernel: [    0.000000] Movable zone start PFN for each node
May 22 15:22:23 riker kernel: [    0.000000] early_node_map[2] active PFN ranges
May 22 15:22:23 riker kernel: [    0.000000]     0: 0x00000000 -> 0x00010000
May 22 15:22:23 riker kernel: [    0.000000]     0: 0x00010800 -> 0x00010800
May 22 15:22:23 riker kernel: [    0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1
May 22 15:22:23 riker kernel: [    0.000000] PERCPU: Embedded 10 pages/cpu @c196f000 s18836 r0 d22124 u65536
May 22 15:22:23 riker kernel: [    0.000000] pcpu-alloc: s18836 r0 d22124 u65536 alloc=16*4096
May 22 15:22:23 riker kernel: [    0.000000] pcpu-alloc: [0] 0 
May 22 15:22:23 riker kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65008
May 22 15:22:23 riker kernel: [    0.000000] Kernel command line: root=/dev/xvda1 ro swiotlb=32,force xencons=tty
May 22 15:22:23 riker kernel: [    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
May 22 15:22:23 riker kernel: [    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
May 22 15:22:23 riker kernel: [    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
May 22 15:22:23 riker kernel: [    0.000000] Enabling fast FPU save and restore... done.
May 22 15:22:23 riker kernel: [    0.000000] Enabling unmasked SIMD FPU exception support... done.
May 22 15:22:23 riker kernel: [    0.000000] Initializing CPU#0
May 22 15:22:23 riker kernel: [    0.000000] Software IO TLB enabled: 
May 22 15:22:23 riker kernel: [    0.000000]  Aperture:     32 megabytes
May 22 15:22:23 riker kernel: [    0.000000]  Address size: 28 bits
May 22 15:22:23 riker kernel: [    0.000000]  Kernel range: c1c8a000 - c3c8a000
May 22 15:22:23 riker kernel: [    0.000000] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
May 22 15:22:23 riker kernel: [    0.000000] Subtract (32 early reservations)
May 22 15:22:23 riker kernel: [    0.000000]   #1 [0001000000 - 00015b5674]   TEXT DATA BSS
May 22 15:22:23 riker kernel: [    0.000000]   #2 [00015c6000 - 000196f000]    Xen provided
May 22 15:22:23 riker kernel: [    0.000000]   #3 [00019c2000 - 0001a38000]         PGTABLE
May 22 15:22:23 riker kernel: [    0.000000]   #4 [0010000000 - 0010800000]         BALLOON
May 22 15:22:23 riker kernel: [    0.000000]   #5 [00015b6000 - 00015b7000]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #6 [0001a38000 - 0001c48000]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #7 [00015b5680 - 00015b5684]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #8 [00015b5700 - 00015b57c0]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #9 [00015b5800 - 00015b5818]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #10 [00015b7000 - 00015b7c00]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #11 [0001c48000 - 0001c8a000]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #12 [00019af000 - 00019c2000]    Xen provided
May 22 15:22:23 riker kernel: [    0.000000]   #13 [00015b8000 - 00015b8008]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #14 [00015b5880 - 00015b5884]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #15 [00015b9000 - 00015ba000]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #16 [00015b5900 - 00015b5930]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #17 [00015b5980 - 00015b59b0]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #18 [000196f000 - 0001979000]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #19 [00015b5a00 - 00015b5a04]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #20 [00015b5a80 - 00015b5a84]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #21 [00015b5b00 - 00015b5b04]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #22 [00015b5b80 - 00015b5b84]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #23 [00015b5c00 - 00015b5c80]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #24 [00015b5c80 - 00015b5cac]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #25 [00015ba000 - 00015bb000]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #26 [0001979000 - 0001999000]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #27 [0001999000 - 00019a9000]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #28 [0001c8a000 - 0003c8a000]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #29 [0003c8a000 - 0003c9a000]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #30 [0003c9a000 - 0003cba000]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000]   #31 [00015bb000 - 00015c3000]         BOOTMEM
May 22 15:22:23 riker kernel: [    0.000000] Initializing HighMem for node 0 (00000000:00000000)
May 22 15:22:23 riker kernel: [    0.000000] Memory: 216380k/270336k available (3317k kernel code, 45764k reserved, 1720k data, 220k init, 0k highmem)
May 22 15:22:23 riker kernel: [    0.000000] virtual kernel memory layout:
May 22 15:22:23 riker kernel: [    0.000000]     fixmap  : 0xf565f000 - 0xf57ff000   (1664 kB)
May 22 15:22:23 riker kernel: [    0.000000]     pkmap   : 0xf5200000 - 0xf5400000   (2048 kB)
May 22 15:22:23 riker kernel: [    0.000000]     vmalloc : 0xd1000000 - 0xf51fe000   ( 577 MB)
May 22 15:22:23 riker kernel: [    0.000000]     lowmem  : 0xc0000000 - 0xd0800000   ( 264 MB)
May 22 15:22:23 riker kernel: [    0.000000]       .init : 0xc14ec000 - 0xc1523000   ( 220 kB)
May 22 15:22:23 riker kernel: [    0.000000]       .data : 0xc133d666 - 0xc14eb698   (1720 kB)
May 22 15:22:23 riker kernel: [    0.000000]       .text : 0xc1000000 - 0xc133d666   (3317 kB)
May 22 15:22:23 riker kernel: [    0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
May 22 15:22:23 riker kernel: [    0.000000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
May 22 15:22:23 riker kernel: [    0.000000] Hierarchical RCU implementation.
May 22 15:22:23 riker kernel: [    0.000000] NR_IRQS:592
May 22 15:22:23 riker kernel: [    0.000000] Xen reported: 2210.036 MHz processor.
May 22 15:22:23 riker kernel: [    0.000000] Console: colour dummy device 80x25
May 22 15:22:23 riker kernel: [    0.000000] console [tty0] enabled
May 22 15:22:23 riker kernel: [    0.000000] console [tty-1] enabled
May 22 15:22:23 riker kernel: [    0.080002] Calibrating delay using timer specific routine.. 4423.38 BogoMIPS (lpj=8846767)
May 22 15:22:23 riker kernel: [    0.080025] Security Framework initialized
May 22 15:22:23 riker kernel: [    0.080030] SELinux:  Initializing.
May 22 15:22:23 riker kernel: [    0.080049] Mount-cache hash table entries: 512
May 22 15:22:23 riker kernel: [    0.080155] Checking 'hlt' instruction... OK.
May 22 15:22:23 riker kernel: [    0.080377] SMP alternatives: switching to UP code
May 22 15:22:23 riker kernel: [    0.095022] Freeing SMP alternatives: 20k freed
May 22 15:22:23 riker kernel: [    0.095174] Brought up 1 CPUs
May 22 15:22:23 riker kernel: [    0.095736] NET: Registered protocol family 16
May 22 15:22:23 riker kernel: [    0.096720] Brought up 1 CPUs
May 22 15:22:23 riker kernel: [    0.096729] PCI: setting up Xen PCI frontend stub
May 22 15:22:23 riker kernel: [    0.098985] bio: create slab <bio-0> at 0
May 22 15:22:23 riker kernel: [    0.099107] vgaarb: loaded
May 22 15:22:23 riker kernel: [    0.099317] suspend: event channel 5
May 22 15:22:23 riker kernel: [    0.099867] xen_mem: Initialising balloon driver.
May 22 15:22:23 riker kernel: [    0.103324] SCSI subsystem initialized
May 22 15:22:23 riker kernel: [    0.103511] usbcore: registered new interface driver usbfs
May 22 15:22:23 riker kernel: [    0.103555] usbcore: registered new interface driver hub
May 22 15:22:23 riker kernel: [    0.103597] usbcore: registered new device driver usb
May 22 15:22:23 riker kernel: [    0.103667] PCI: System does not support PCI
May 22 15:22:23 riker kernel: [    0.103673] PCI: System does not support PCI
May 22 15:22:23 riker kernel: [    0.103791] NetLabel: Initializing
May 22 15:22:23 riker kernel: [    0.103796] NetLabel:  domain hash size = 128
May 22 15:22:23 riker kernel: [    0.103799] NetLabel:  protocols = UNLABELED CIPSOv4
May 22 15:22:23 riker kernel: [    0.103811] NetLabel:  unlabeled traffic allowed by default
May 22 15:22:23 riker kernel: [    0.103817] Switching to clocksource xen
May 22 15:22:23 riker kernel: [    0.105826] pcifront pci-0: Installing PCI frontend
May 22 15:22:23 riker kernel: [    0.105972] pcifront pci-0: Creating PCI Frontend Bus 0000:00
May 22 15:22:23 riker kernel: [    0.109948] NET: Registered protocol family 2
May 22 15:22:23 riker kernel: [    0.109995] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
May 22 15:22:23 riker kernel: [    0.110144] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
May 22 15:22:23 riker kernel: [    0.110180] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
May 22 15:22:23 riker kernel: [    0.110216] TCP: Hash tables configured (established 8192 bind 8192)
May 22 15:22:23 riker kernel: [    0.110221] TCP reno registered
May 22 15:22:23 riker kernel: [    0.110225] UDP hash table entries: 128 (order: 0, 4096 bytes)
May 22 15:22:23 riker kernel: [    0.110234] UDP-Lite hash table entries: 128 (order: 0, 4096 bytes)
May 22 15:22:23 riker kernel: [    0.110283] NET: Registered protocol family 1
May 22 15:22:23 riker kernel: [    0.110358] RPC: Registered udp transport module.
May 22 15:22:23 riker kernel: [    0.110362] RPC: Registered tcp transport module.
May 22 15:22:23 riker kernel: [    0.110366] RPC: Registered tcp NFSv4.1 backchannel transport module.
May 22 15:22:23 riker kernel: [    0.110450] Trying to unpack rootfs image as initramfs...
May 22 15:22:23 riker kernel: [    0.114753] Freeing initrd memory: 3748k freed
May 22 15:22:23 riker kernel: [    0.116206] platform rtc_cmos: registered platform RTC device (no PNP device found)
May 22 15:22:23 riker kernel: [    0.116594] audit: initializing netlink socket (disabled)
May 22 15:22:23 riker kernel: [    0.116609] type=2000 audit(1306070532.905:1): initialized
May 22 15:22:23 riker kernel: [    0.118341] VFS: Disk quotas dquot_6.5.2
May 22 15:22:23 riker kernel: [    0.118401] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
May 22 15:22:23 riker kernel: [    0.119145] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
May 22 15:22:23 riker kernel: [    0.119363] NTFS driver 2.1.29 [Flags: R/W].
May 22 15:22:23 riker kernel: [    0.119545] msgmni has been set to 519
May 22 15:22:23 riker kernel: [    0.119935] alg: No test for stdrng (krng)
May 22 15:22:23 riker kernel: [    0.120046] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
May 22 15:22:23 riker kernel: [    0.120053] io scheduler noop registered
May 22 15:22:23 riker kernel: [    0.120057] io scheduler deadline registered
May 22 15:22:23 riker kernel: [    0.120069] io scheduler cfq registered (default)
May 22 15:22:23 riker kernel: [    0.120169] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
May 22 15:22:23 riker kernel: [    0.121626] brd: module loaded
May 22 15:22:23 riker kernel: [    0.122312] loop: module loaded
May 22 15:22:23 riker kernel: [    0.124601] Xen virtual console successfully installed as tty1
May 22 15:22:23 riker kernel: [    0.140588] netfront: Initialising virtual ethernet driver.
May 22 15:22:23 riker kernel: [    0.143341] xen-vbd: registered block device major 202
May 22 15:22:23 riker kernel: [    0.143374] blkfront: xvda1: barriers enabled
May 22 15:22:23 riker kernel: [    0.144490] Setting capacity to 4194304
May 22 15:22:23 riker kernel: [    0.144499] xvda1: detected capacity change from 0 to 2147483648
May 22 15:22:23 riker kernel: [    0.146980] blkfront: xvda2: barriers enabled
May 22 15:22:23 riker kernel: [    0.148139] blkfront: xvdb1: barriers enabled
May 22 15:22:23 riker kernel: [    0.148469] Setting capacity to 2097152
May 22 15:22:23 riker kernel: [    0.148477] xvda2: detected capacity change from 0 to 1073741824
May 22 15:22:23 riker kernel: [    0.148598] Setting capacity to 2930272002
May 22 15:22:23 riker kernel: [    0.148603] xvdb1: detected capacity change from 0 to 1500299265024
May 22 15:22:23 riker kernel: [    0.149208] console [netcon0] enabled
May 22 15:22:23 riker kernel: [    0.149213] netconsole: network logging started
May 22 15:22:23 riker kernel: [    0.149228] Initializing USB Mass Storage driver...
May 22 15:22:23 riker kernel: [    0.149275] usbcore: registered new interface driver usb-storage
May 22 15:22:23 riker kernel: [    0.149279] USB Mass Storage support registered.
May 22 15:22:23 riker kernel: [    0.149341] usbcore: registered new interface driver libusual
May 22 15:22:23 riker kernel: [    0.150207] mice: PS/2 mouse device common for all mice
May 22 15:22:23 riker kernel: [    0.150319] Netfilter messages via NETLINK v0.30.
May 22 15:22:23 riker kernel: [    0.150339] nf_conntrack version 0.5.0 (4154 buckets, 16616 max)
May 22 15:22:23 riker kernel: [    0.150494] ctnetlink v0.93: registering with nfnetlink.
May 22 15:22:23 riker kernel: [    0.150898] ip_tables: (C) 2000-2006 Netfilter Core Team
May 22 15:22:23 riker kernel: [    0.150924] TCP cubic registered
May 22 15:22:23 riker kernel: [    0.150927] Initializing XFRM netlink socket
May 22 15:22:23 riker kernel: [    0.151166] NET: Registered protocol family 10
May 22 15:22:23 riker kernel: [    0.151862] ip6_tables: (C) 2000-2006 Netfilter Core Team
May 22 15:22:23 riker kernel: [    0.152048] IPv6 over IPv4 tunneling driver
May 22 15:22:23 riker kernel: [    0.152543] NET: Registered protocol family 17
May 22 15:22:23 riker kernel: [    0.252221] Freeing unused kernel memory: 220k freed
May 22 15:22:23 riker kernel: [    0.254689] Write protecting the kernel text: 3320k
May 22 15:22:23 riker kernel: [    0.255726] Write protecting the kernel read-only data: 1420k
May 22 15:22:23 riker kernel: [    0.741489] kjournald starting.  Commit interval 5 seconds
May 22 15:22:23 riker kernel: [    0.741519] EXT3-fs (xvda1): mounted filesystem with writeback data mode
May 22 15:22:23 riker kernel: [    3.528792] udevd version 125 started
May 22 15:22:23 riker kernel: [    4.735952] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully
May 22 15:22:23 riker kernel: [    4.755484] flexcop-pci: will use the HW PID filter.
May 22 15:22:23 riker kernel: [    4.755590] flexcop-pci: card revision 2
May 22 15:22:23 riker kernel: [    4.755631] b2c2_flexcop_pci 0000:00:02.0: enabling device (0000 -> 0003)
May 22 15:22:23 riker kernel: [    4.776436] DVB: registering new adapter (FlexCop Digital TV device)
May 22 15:22:23 riker kernel: [    4.781600] b2c2-flexcop: MAC address = 00:d0:d7:08:0c:bc
May 22 15:22:23 riker kernel: [    4.822306] Linux video capture interface: v2.00
May 22 15:22:23 riker kernel: [    4.873836] saa7146: register extension 'budget_av'.
May 22 15:22:23 riker kernel: [    4.881785] saa7146: register extension 'budget_ci dvb'.
May 22 15:22:23 riker kernel: [    5.102509] mt352_read_register: readreg error (reg=127, ret==-121)
May 22 15:22:23 riker kernel: [    5.116089] nxt200x: nxt200x_readbytes: i2c read error (addr 0x0a, err == -121)
May 22 15:22:23 riker kernel: [    5.116125] Unknown/Unsupported NXT chip: 00 00 00 00 00
May 22 15:22:23 riker kernel: [    5.125472] lgdt330x: i2c_read_demod_bytes: addr 0x59 select 0x02 error (ret == -121)
May 22 15:22:23 riker kernel: [    5.158868] b2c2-flexcop: found 'ST STV0297 DVB-C' .
May 22 15:22:23 riker kernel: [    5.158889] DVB: registering adapter 0 frontend 0 (ST STV0297 DVB-C)...
May 22 15:22:23 riker kernel: [    5.158946] b2c2-flexcop: initialization of 'Cable2PC/CableStar 2 DVB-C' at the 'PCI' bus controlled by a 'FlexCopIIb' complete
May 22 15:22:23 riker kernel: [    5.161517] budget_av 0000:00:00.0: enabling device (0000 -> 0002)
May 22 15:22:23 riker kernel: [    5.161637] IRQ 19/: IRQF_DISABLED is not guaranteed on shared IRQs
May 22 15:22:23 riker kernel: [    5.161696] saa7146: found saa7146 @ mem d130e000 (revision 1, irq 19) (0x1894,0x002c).
May 22 15:22:23 riker kernel: [    5.161706] saa7146 (0): dma buffer size 1347584
May 22 15:22:23 riker kernel: [    5.161711] DVB: registering new adapter (Satelco EasyWatch DVB-C MK3)
May 22 15:22:23 riker kernel: [    5.197143] adapter failed MAC signature check
May 22 15:22:23 riker kernel: [    5.197159] encoded MAC from EEPROM was ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff
May 22 15:22:23 riker kernel: [    5.460468] KNC1-1: MAC addr = 00:09:d6:6d:b0:33
May 22 15:22:23 riker kernel: [    5.629000] DVB: registering adapter 1 frontend 0 (Philips TDA10023 DVB-C)...
May 22 15:22:23 riker kernel: [    5.630320] budget-av: ci interface initialised.
May 22 15:22:23 riker kernel: [    5.630922] budget_ci dvb 0000:00:01.0: enabling device (0000 -> 0002)
May 22 15:22:23 riker kernel: [    5.631168] IRQ 18/: IRQF_DISABLED is not guaranteed on shared IRQs
May 22 15:22:23 riker kernel: [    5.631284] saa7146: found saa7146 @ mem d159a000 (revision 1, irq 18) (0x13c2,0x1010).
May 22 15:22:23 riker kernel: [    5.631317] saa7146 (1): dma buffer size 1347584
May 22 15:22:23 riker kernel: [    5.631334] DVB: registering new adapter (TT-Budget-C-CI PCI)
May 22 15:22:23 riker kernel: [    5.665315] adapter has MAC addr = 00:d0:5c:67:c4:ab
May 22 15:22:23 riker kernel: [    5.667237] input: Budget-CI dvb ir receiver saa7146 (1) as /devices/xen/pci-0/pci0000:00/0000:00:01.0/input/input0
May 22 15:22:23 riker kernel: [    5.667690] Creating IR device irrcv0
May 22 15:22:23 riker kernel: [    5.667997] DVB: registering adapter 2 frontend 0 (ST STV0297 DVB-C)...
May 22 15:22:23 riker kernel: [    6.090682] Adding 1048572k swap on /dev/xvda2.  Priority:-1 extents:1 across:1048572k SS
May 22 15:22:23 riker kernel: [    6.138383] EXT3-fs (xvda1): warning: maximal mount count reached, running e2fsck is recommended
May 22 15:22:23 riker kernel: [    6.147026] EXT3-fs (xvda1): using internal journal
May 22 15:22:23 riker kernel: [    7.303776] kjournald starting.  Commit interval 5 seconds
May 22 15:22:23 riker kernel: [    7.306162] EXT3-fs (xvdb1): using internal journal
May 22 15:22:23 riker kernel: [    7.306198] EXT3-fs (xvdb1): mounted filesystem with writeback data mode
May 22 15:22:25 riker kernel: [   12.483577] svc: failed to register lockdv1 RPC service (errno 97).
May 22 15:22:25 riker kernel: [   12.486456] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory

[-- 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] 17+ messages in thread

* Re: Re: AW: Load increase after memory upgrade?
  2011-06-27 19:56   ` Carsten Schiers
@ 2011-06-28 14:49     ` Konrad Rzeszutek Wilk
  0 siblings, 0 replies; 17+ messages in thread
From: Konrad Rzeszutek Wilk @ 2011-06-28 14:49 UTC (permalink / raw)
  To: Carsten Schiers; +Cc: xen-devel

On Mon, Jun 27, 2011 at 09:56:38PM +0200, Carsten Schiers wrote:
> >Um, so 2.6.34 to 2.6.32 causes this spike in usage? 
> 
> Definitely yes. 

What happens if you remove the extra 4GB of memory? You mentioned you did
two things: a) more memory and b) change kernel versions.

Need to narrow down which one is at fault here.
> 
> > What is the SWIOTLB (PCI-DMA32) usage between these two kernels 
> 
> I don't understand. What do you mean? The only difference is that I call 
> up the swiotlb differently:
> 
> On pvops: iommu=soft

so 64MB here
> On rebased: swiotlb=32,force

32MB here.

Which is OK. I was somehow thinking you might have a small amount of
memory in the pvops case - but you actually have a pretty big buffer there.

> 
> BTW: changing to 64,force doesn't make a difference.

<nods> So DMA might not be an issue here..
> 
> I attached a normal boot log of both kernels.
> 
> > and are the drivers (budget_...) the same version?
> 
> No, but a quick diff between the two source trees offer only minor 
> changes that from the first look
> do not seem to be related to DMA or whatever.
> 
> Carsten.
> 
> 



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

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

end of thread, other threads:[~2011-06-30 22:00 UTC | newest]

Thread overview: 17+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-06-27 11:29 AW: Load increase after memory upgrade? Carsten Schiers
2011-06-27 13:46 ` Konrad Rzeszutek Wilk
2011-06-27 15:37   ` Sander Eikelenboom
2011-06-27 20:00     ` AW: " Carsten Schiers
2011-06-27 20:20       ` Sander Eikelenboom
2011-06-27 20:44         ` AW: " Carsten Schiers
2011-06-27 20:46         ` Carsten Schiers
2011-06-28 14:57           ` Konrad Rzeszutek Wilk
2011-06-28 20:17             ` AW: " Carsten Schiers
2011-06-28 20:22             ` Carsten Schiers
2011-06-28 20:34               ` Konrad Rzeszutek Wilk
2011-06-29 21:17                 ` AW: " Carsten Schiers
2011-06-30 22:00                   ` Konrad Rzeszutek Wilk
2011-06-28 14:50       ` Konrad Rzeszutek Wilk
2011-06-28 20:34     ` AW: " Carsten Schiers
2011-06-27 19:56   ` Carsten Schiers
2011-06-28 14:49     ` 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.