Bug#672959: kfreebsd-*: panic: vm_fault_copy_wired

2012-05-14 Thread Steven Chamberlain
Package: src:sysvinit Version: 2.88dsf-22.1 Severity: important Tags: sid wheezy User: debian-bsd@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-bsd@lists.debian.org Hi, Not exactly sure yet where to file this bug, perhaps initscripts, a kernel (kfreebsd-8 and -9) bug or something else

Re: panic: vm_fault_copy_wired

2012-05-14 Thread Dererk
On 14/05/12 17:08, Steven Chamberlain wrote: > Hi, > > This problem came back after an unclean, forced reset of a crashed VM. > This time I managed to log startup messages via serial console. > > After this problem occurred, it would persist between resets. I had to > boot d-i, drop to a shell, ru

Re: Bug#667755: aiccu: FTBFS[kfreebsd]:

2012-05-14 Thread Steven Chamberlain
Hi, Builds okay for me too on Wheezy kfreebsd-i386 (gcc-4.7, kkh 9.0-1) using dpkg-buildpackage... But I noticed this in the buildd log, during a debian/rules clean step: https://buildd.debian.org/status/fetch.php?pkg=aiccu&arch=kfreebsd-i386&ver=20070115-15&stamp=1333022804 > Removing patch 04_

Re: panic: vm_fault_copy_wired

2012-05-14 Thread Christoph Egger
Hi! Steven Chamberlain writes: > This problem came back after an unclean, forced reset of a crashed VM. > This time I managed to log startup messages via serial console. > > After this problem occurred, it would persist between resets. I had to > boot d-i, drop to a shell, run fsck.ufs -y on the

Re: panic: vm_fault_copy_wired

2012-05-14 Thread Steven Chamberlain
Hi, This problem came back after an unclean, forced reset of a crashed VM. This time I managed to log startup messages via serial console. After this problem occurred, it would persist between resets. I had to boot d-i, drop to a shell, run fsck.ufs -y on the root partition (this just marked it

Re: OpenJDK-7 on kFreeBSD (feedback)

2012-05-14 Thread Steven Chamberlain
Hi Damien, I've been trying again with newer openjdk-7 7~u3-2.1.1~pre1-2, using dpkg-buildpackage, and keeping a log this time of a single build attempt, immediately after extracting from source. With -j2 I am seeing this error first: > Error: entry is missing!!! > > Error: entry is missing