-Original Message-
From: Konrad Rzeszutek Wilk [mailto:konrad.w...@oracle.com]
Sent: Monday, September 20, 2010 6:08 PM
To: Artur Linhart - Linux communication
Cc: 'Ian Campbell'; 596...@bugs.debian.org
Subject: Re: Bug#596419: Acknowledgement (xen-linux-system-2.6.32-5-xen-amd64:
causes
So, it worked if I have specified in Dom0 in the baloon mode by omitting
the specification of dom0_mem or, if dom0_mem is specified then also the
swiotlb=65536 must be specified.
Wow. That implies that AACRAID uses quite a lot of buffers, and looking at the
driver
there are a bunch of quirks
(Konrad, this looks potentially swiotlb like, what do you think? Full
bug log is at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596419 )
On Sun, 2010-09-12 at 07:58 +0200, Artur Linhart - Linux communication wrote:
Even after the downgrade of kernel and of the corresponding files to the
Hello, Ian,
your theory with the out-of-memory seems to be the step into the
right direction.
It looks like the problems did not really start with the
instalaltion of the new packages, but with the set of the xen kernel
parameter
dom0_mem=1024M
which I made approximatelly at the
Even after the downgrade of kernel and of the corresponding files to the
version 2.6.32-18 and downgrade of mdadm the problem still persists, so it
is not bound specificallz to this package and to this version.
I have identified now (after the downgrades to 2.6.30-18) the following
initial
One more remark - the last tests from the previous post were done on the
synced array, so there was not other heavy load on it at the time of this
last crash. The crash happened also during the
xendomains stop
before the system shutdown. It happened not immediatelly, but first after
sime time
On Sun, 2010-09-12 at 07:58 +0200, Artur Linhart - Linux communication
wrote:
Even after the downgrade of kernel and of the corresponding files to the
version 2.6.32-18 and downgrade of mdadm the problem still persists, so it
is not bound specificallz to this package and to this version.
[...]
Hello,
If booting on non-xen kernel, then no problems can be seen. But it
is true, exactly the same asction cannot be tested, the xendomains script
can be started only if running under xen and also there had to be some
virtual instances to be suspended...
If I boot with xen and
After further anaysis it seems to be the fact it occurs not by mdadm stop
but by the call of xendomains stop because the hangup occurs not only by
the shutdown, but also by the simple call of
/etc/init.d/xendomains stop
- there are 4 domains running, 3 fully virtualized based on qemu and one
Additional info:
Downgrading of the package and kernel image to 2.6.35-18 did not helped,
Running of
/etc/init.d/xendomains stop
Still brought an error, containing also following message:
kernel bug /source_amd_xen/drivers/scsi/aacraid/aachba.c:2825!
(the dots were not there, there
10 matches
Mail list logo
