On 20 August 2014 15:56, Steven Chamberlain wrote:
> Hi,
>
> I've tested for this vt(4) issue in upstream's own kernel build from:
> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/10.0-STABLE
> and it is affected as well. It is only a problem when using Qemu with
> the "-enable-kvm" option (an
Control: tags -1 + patch
Hi,
The simple patch for this issue is as follows. It has been tested now
on kfreebsd-amd64 and kfreebsd-i386 with varying amounts of available
RAM.
* On kfreebsd, use dynamically-sized tmpfs for:
- /var/cache/anna
- /var/lib/cdebconf
to avoid running out
Cyril Brulebois, le Thu 21 Aug 2014 02:03:48 +0200, a écrit :
> Steven Chamberlain (2014-08-21):
> > On 21/08/14 00:23, Steven Chamberlain wrote:
> > > Using qemu-system-i386 with the -smp 2 flag, I started seeing weird
> > > issues early in d-i:
> >
> > It seems more likely this was triggered by
Processing commands for cont...@bugs.debian.org:
> retitle 758757 kfreebsd-10: d-i bugs caused by qemu-system-i386
Bug #758757 [kernel-image-10.0-1-486-di] kfreebsd-10: d-i bugs caused by
qemu-system-i386+kvm
Changed Bug title to 'kfreebsd-10: d-i bugs caused by qemu-system-i386' from
'kfreebsd-
retitle 758757 kfreebsd-10: d-i bugs caused by qemu-system-i386
thanks
Now I think these are two separate issues:
* -smp 2 or higher, triggers the process hand with "sigreturn eflags"
kernel messages, after a few minutes of CPU work
* -enable-kvm triggers memory or file I/O corruption much soone
Steven Chamberlain (2014-08-21):
> retitle 758757 kfreebsd-10: d-i bugs caused by qemu-system-i386+kvm
> thanks
>
> On 21/08/14 00:23, Steven Chamberlain wrote:
> > Using qemu-system-i386 with the -smp 2 flag, I started seeing weird
> > issues early in d-i:
>
> It seems more likely this was trig
Processing commands for cont...@bugs.debian.org:
> retitle 758757 kfreebsd-10: d-i bugs caused by qemu-system-i386+kvm
Bug #758757 [kernel-image-10.0-1-486-di] kfreebsd-10: d-i bugs caused by
qemu-system-i386+smp
Changed Bug title to 'kfreebsd-10: d-i bugs caused by qemu-system-i386+kvm'
from 'k
retitle 758757 kfreebsd-10: d-i bugs caused by qemu-system-i386+kvm
thanks
On 21/08/14 00:23, Steven Chamberlain wrote:
> Using qemu-system-i386 with the -smp 2 flag, I started seeing weird
> issues early in d-i:
It seems more likely this was triggered by -enable-kvm (on a wheezy
linux-amd64 host
Package: kernel-image-10.0-1-486-di
Version: 10.0-6
Severity: important
Affects: debian-installer
X-Debbugs-Cc: debian-b...@lists.debian.org
Hi,
Using qemu-system-i386 with the -smp 2 flag, I started seeing weird
issues early in d-i: a boot-time generated file
/var/lib/cdebconf/templates.dat bei
Hi,
I've tested for this vt(4) issue in upstream's own kernel build from:
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/10.0-STABLE
and it is affected as well. It is only a problem when using Qemu with
the "-enable-kvm" option (and some virtualisation platforms will do this) :
On 08/08/14 01
On 20/08/14 20:27, Ed Maste wrote:
> You can grab a snapshot build from:
> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/10.0-STABLE
Perfect, thanks a lot.
That shows the bug as well, only with -net nic,model=virtio.
Screenshot attached (the serial console didn't seem to work).
I could file
On 20 August 2014 09:38, Steven Chamberlain wrote:
>
> Is there someplace to get 'official' upstream 10-STABLE kernels? Mine
> are built with Debian's usual config and packaging, and Clang 3.4. Thanks!
You can grab a snapshot build from:
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/10.0-ST
On Wed, 20 Aug 2014, Jörg Frings-Fürst wrote:
> Hello,
>
> I have a question about this bug[1].
>
> There are no changes at sysdeputil.c between vsftpd/3.0.2-14 and
> vsftpd/3.0.2-15.
>
> Have one a hint where I must search this problem?
>
> Many thanks...
>
> CU
> Jörg
>
>
> build error
Hello,
I have a question about this bug[1].
There are no changes at sysdeputil.c between vsftpd/3.0.2-14 and
vsftpd/3.0.2-15.
Have one a hint where I must search this problem?
Many thanks...
CU
Jörg
build error
gcc -c sysdeputil.c -g -O2 -fstack-protector --param=ssp-buffer-size=4
Hi,
I've been seeing this panic with 10-STABLE kfreebsd-amd64 snapshots from
the past two weeks or more (but not affecting our 10.0 kernel). The
stack trace implicated atkbd, but I've just discovered it only happens
in Qemu with -net nic,model=virtio and not with model=e1000.
Is there someplace
On 20/08/14 03:59, Cyril Brulebois wrote:
> your package needs an update for the transition to xorg-server 1.16
> which happened in July.
This is something any uploading DD can help with.
Please could someone build and upload xserver-xorg-video-nv 1:2.1.20-3
on kfreebsd-amd64 and kfreebsd-i386, f
On 20/08/14 04:07, Cyril Brulebois wrote:
> Is this going to happen?
I will communicate with debian-boot@ and debian-release@ about this,
this weekend.
> On a slightly related note, looking at the debian-bsd@ DDPO page[1], I
> see some packages are still numbered 8.x or 9.x; does that mean they'r
Hi Steven,
FWIW from my POV the workarounds I implemented in tcpdump and libpcap
aren't long-term solutions, these bugs need to be fixed in time for
jessie, and thus need to be 'serious'. I only added the workarounds to
avoid having my testing migrations blocked by kfreebsd.
As things stand now,
At Tue, 19 Aug 2014 23:41:22 +0200,
Werner Koch wrote:
> On older Linux kernels you had to install gpg suid(root) to allow
> mlock() to work (gpg will drop the permissions right after allocating
> and locking the memory). Recent Linux kernels grant each process a
> certain amount of mlock()-able m
On Wed, Aug 20, 2014 at 01:19:52AM +0100, Steven Chamberlain wrote:
> On 14/08/14 18:15, Cyril Brulebois wrote:
> > [...] If a
> > single extra udeb (or udeb size increase, which happens from time to
> > time) is going to break kfreebsd-*, it seems to me that their status
> > is far too brittle.
>
20 matches
Mail list logo
