On Mon, Apr 15, 2013 at 01:47:28AM +0100, Ben Hutchings wrote:
On Sun, 2013-04-14 at 23:41 +0200, Aurelien Jarno wrote:
[...]
Sorry to answer late, I only have been able to test it now.
Unfortunately the vexpress image is now broken, due to this change:
| * Replace nic-modules with
On Wed, 2013-04-10 at 08:17 -0400, Anthony Sheetz wrote:
Steps to reproduce:
Install Debian Testing from Netinstall CD, amd64.
Choose LVM and Full Disk Encryption, with a separate /home
Resize /home to be 80GB
Install openswan, connect to remote network
Install xen
Set up a virtual machine
(Just sending a copy to BTS)
On Mon, 2013-04-15 at 08:20 -0400, Anthony Sheetz wrote:
All correct, Ian, thanks.
On Mon, Apr 15, 2013 at 5:00 AM, Ian Campbell i...@hellion.org.uk
wrote:
On Sat, 2013-04-13 at 19:48 +0800, Thomas Goirand wrote:
On 04/10/2013 10:49 PM,
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 the local network -
never had a problem with those.
So this issue isn't the tunnel, good.
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
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
(rootflags= on
command line I think? No idea how one inserts
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
Same here on a Acer Aspire V3-771G, notebook work fine with the 3.2.39-2
kernel.
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM
Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core
processor PCI Express Root Port (rev 09)
00:02.0 VGA
On 14.04.2013 18:51, Ben Hutchings wrote:
On Sun, 2013-04-14 at 16:56 +0200, colliar wrote:
This is probably a duplicate of #703715 but the severity should be
raised like the reporter of #703715 already mentioned.
It freezes a system constantly with potential data loss.
Do not get me wrong I
I: Bus=0011 Vendor=0002 Product=0001 Version=
N: Name=PS/2 Generic Mouse
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input12
U: Uniq=
H: Handlers=mouse0 event12
B: PROP=0
B: EV=7
B: KEY=7 0 0 0 0
B: REL=3
input: name = mouse0, path =
Hi Ben,
I did the following test this weekend:
-Power off the machine
-Remove the USB dongle (taint?)
-Power up the machine
-Log in and run doxygen as before
It still crashes. This is, seemingly, the related message:
Apr 14 06:37:59 Debianosaur kernel: [137278.487402] doxygen[2535]:
segfault at
Hello Aurélien!
Aurelien Jarno aure...@debian.org (14/04/2013):
Sorry to answer late, I only have been able to test it now.
Unfortunately the vexpress image is now broken, due to this change:
| * Replace nic-modules with nic-{usb,wireless}-modules in armhf netboot
|images (Closes:
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
On Mon, Apr 15, 2013 at 10:34:03AM +0200, Aurelien Jarno wrote:
On Mon, Apr 15, 2013 at 01:47:28AM +0100, Ben Hutchings wrote:
On Sun, 2013-04-14 at 23:41 +0200, Aurelien Jarno wrote:
[...]
Sorry to answer late, I only have been able to test it now.
Unfortunately the vexpress image is
Package: nfs-common
Version: 1:1.2.6-3
Severity: normal
Mounting a kerberos-protected nfs4 export is unsuccsessfull on powerpcspe.
nfs-common initializes without error, and rpc.gssd appears to be running. Upon
a mount attempt, the following error message was displayed:
mount: fstab path:
On Mon, 2013-04-15 at 15:53 +0200, colliar wrote:
On 14.04.2013 18:51, Ben Hutchings wrote:
[...]
No, see http://kernel-handbook.alioth.debian.org/ch-bugs.html#s9.1.2
I see. So it is up to the kernel team to decide which hardware is new
and which not ? Are there any guidelines, introduced ~
16 matches
Mail list logo
