Bug should be assigned to Debian stable, not Debian oldstable. This bug
happens with Wheezy dom0 and domU.
I believe that bug 705124 should be associated with the current stable
kernel, not the old stable kernel. The problem is found on Debian 7.0 with
either a Debian 6.0 or Debian 7.0 domU.
How do we get this re-assigned to current stable, and how do we get
attention brought to it for a resolution?
Tried wheezy domU on wheezy dom0 - same bug exhibited itself.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Any other ideas on how to move forward with this bug?
On Wed, Apr 17, 2013 at 8:57 AM, Ian Campbell i...@hellion.org.uk wrote:
On Tue, 2013-04-16 at 09:39 -0400, Anthony Sheetz wrote:
What does dom0 dmesg say about barriers on that
device/filesystem?
Nothing in dmesg about
Replies in line.
On Mon, Apr 15, 2013 at 9:09 AM, Ian Campbell i...@hellion.org.uk wrote:
On Mon, 2013-04-15 at 08:19 -0400, Anthony Sheetz wrote:
Did you ever happen to try a transfer over a
non-tunnelled connection?
Yes, tried file transfers from another machine
On Mon, Apr 15, 2013 at 9:29 AM, Ian Campbell i...@hellion.org.uk wrote:
On Mon, 2013-04-15 at 09:21 -0400, Anthony Sheetz wrote:
How did you do this? IIRC getting mount options to the root
filesystem
to take effect involves more than just editing fstab
Current status.
New laptop hard drive purchased and installed.
Experiment 1
Instead of LVM with full disk encryption, have used LVM without full disk
encryption.
Instead of transferring file to the lv used for DomU '/', have created a
new lv mounted with 'mount /dev/xvda3 /mnt' insided DomU to
Alas, I do not have the Thinkpad any more - had to return it. I've since
had to install Debian Stable on the ASUS. Output of lspci and dmidecode are
from that version - fair warning.
demidecode output is attached.
lspci from the Asus:
00:00.0 Host bridge: Intel Corporation Device 0154 (rev 09)
8 matches
Mail list logo
