Package: src:linux
Version: 4.6.4-1~bpo8+1
Severity: important
Problem occurs on the notebook display only, the attached screen display does
no flickering at all with any kernel tried. After the last version of package
the flickering is very massive after the boot of the system and start of
X-Wind
> Thanks for reporting this and sorry for the long quiet. Can you
> reproduce this using a sid kernel for the dom0? I think the only
> packages that should be needed for this test from outside squeeze are
> the kernel image itself, linux-base, and initramfs-tools.
>
> Jonathan
Hello, Jonathan,
One more correctlion to my last message - I have figured out, some instances
have had still the kernel from version 2.6.32-21 what
was the reason why they started correctly... So it seems the effect can be seen
on all DomUs with the kernel from package version
2.6.32-27
--
To UNSUBSCRIBE, e
tween them...
Unfortunately, I will not have the chance to test the patch directly, I use
vanilla kernel from the package only...
-Original Message-
From: Timo Juhani Lindfors [mailto:timo.lindf...@iki.fi]
Sent: Wednesday, November 17, 2010 2:11 PM
To: Artur Linhart
Cc: 603...@bugs.debian.o
Additional info - I figured out, the domain is paused only, so after calling of
xm unpause
the domain continues to respond and to run.
So, maybe it is not a bug, but a feature?
If it is so, then there should be a possibility to start the domain
immediatelly.
One more remark: It does not affect
Package: linux-2.6
Version: 2.6.32-27
Severity: important
If the kernel is used for paravirtual DomU, then the DomU is normally started
orshutdown. Ifthe xm save and xm restore
is invoked explicitely,then the DomU also restores normally. Only in the case
the DomU is
restored automatically via
>-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-lin
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
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 the
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 (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 stack
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 wa
o some message with aacraid, but It
vanished too quickly to see what was written there.
-----Original Message-
From: Debian BTS [mailto:debb...@busoni.debian.org] On Behalf Of Debian Bug
Tracking System
Sent: Saturday, September 11, 2010 10:15 AM
To: Artur Linhart
Subject: Bug#596419: Acknowledgemen
This bug is a duplicate of the bug 596419, so it can be closed.
-Original Message-
From: Debian BTS [mailto:debb...@busoni.debian.org] On Behalf Of Debian Bug
Tracking System
Sent: Saturday, September 11, 2010 11:06 AM
To: Artur Linhart
Subject: Bug#596422: Acknowledgement (xen-linux
Package: xen-linux-system-2.6.32-5-xen-amd64
Version: 2.6.32-21
Severity: critical
Justification: causes serious data loss
During the shutdown there comes a system hangup somehow related to aacraid.
It first came now after the upgrade of the package to the version specified
below.
It makes it im
Package: xen-linux-system-2.6.32-5-xen-amd64
Version: 2.6.32-21
Severity: critical
Justification: breaks the whole system
On the system is installed sw raid, raid1 is used.
There are 3 RAID1 volumes made as partition mirroring of 3 partitions,
1. for the system (is installed there), 2. and 3. for
16 matches
Mail list logo
