On 2013-06-14 23:07:02 (+0200), Alexander Leidinger alexan...@leidinger.net
wrote:
The bt in the minidump is useless, but I made a bt directly
in the kernel debugger:
---snip---
Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 02
fault virtual address = 0x0
fault code
On Fri, Jun 21, 2013 at 08:17:12PM -0400, Glen Barber wrote:
G Hi,
G
G I have the following kgdb session from a page fault seemingly triggered
G in pf(4).
pfslowtimo() isn't related to pf(4). pf stands here for protocol family.
G (kgdb) list *0x80772688
G 0x80772688 is in
On Mon, Jun 24, 2013 at 02:21:56PM +0400, Gleb Smirnoff wrote:
On Fri, Jun 21, 2013 at 08:17:12PM -0400, Glen Barber wrote:
G Hi,
G
G I have the following kgdb session from a page fault seemingly triggered
G in pf(4).
pfslowtimo() isn't related to pf(4). pf stands here for protocol
I've started seeing these on multiple machines in the last few days when
building pretty much any port:
+pid 23141 (dialog4ports), uid 0: exited on signal 6 (core dumped)
+pid 23394 (dialog4ports), uid 0: exited on signal 6 (core dumped)
+pid 23782 (dialog4ports), uid 0: exited on signal 6
I've noticed that dialog4ports has been crashing pretty consistently recently.
Happening to anyone else?
Dan
root@winbsd:/usr/ports/net-mgmt # cd zabbix2-agent/
root@winbsd:/usr/ports/net-mgmt/zabbix2-agent # ls
Makefiledialog4ports.core
Hi,
It's (transcribed):
kern.timecounter.hardware: TSC
kern.timecounter.choice: TSC(1000) ACPI-fast (900) HPET (950) i8254
(0) dummy(-1000)
kern.timecounter.tick: 1
kern.timecounter.fast_gettime: 1
kern.timecounter.invariant_tsc: 1
kern.timecounter.smp_tsc: 1
kern.timecounter.smp_tsc_adjust: 0
Yep, got it. Sorry for the multiple posts ... we lost power and my mail
server switched sites causing a temporary loss of trust between me and the
freebsd.org mail servers.
Thanks for all the help,
Dan
On Mon, 24 Jun 2013, Ilya A. Arkhipov wrote:
Hi Dan,
libdialog was bumped svn
On Mon, 24 Jun 2013 12:15:18 +0200
Kristof Provost kris...@sigsegv.be wrote:
For what it's worth, I'm running into exactly the same problem.
(amd64, stable/9). I have no custom settings in /etc/make.conf
or /etc/src.conf
I had a short discussion with the maintainer of our stress-test-suite,
I recently upgraded my main buildbox from an ancient 9.0-STABLE snapshot
to head and I've run into an issue building 9-STABLE on it. Initally
this was broken by the switch to bmake, but Simon committed a work
around that and using the fmake port also works around it. Now I'm
seeing a strange
On Mon, Jun 17, 2013 at 7:14 PM, Isabell Long iss...@freebsd.org wrote:
It's that time again! On behalf of monthly@, I would like to inform
you that the next submission date for the April to June quarterly
status reports is July 7th, 2013 - less than a month away.
Note that you have a little
Hello-
I am running 10.0-CURRENT #0 r252098 on a beaglebone and I am getting the
occasional LOR when reading/writing in an nfs mount
lock order reversal:
1st 0xc1c0a150 newnfs (newnfs) @ /usr/src/sys/kern/vfs_syscalls.c:4064
2nd 0xc6a5e278 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2311
Hello list,
I was forced to run -CURRENT because no other version booted in my new
box.
Running 10.0-CURRENT FreeBSD 10.0-CURRENT #1: Wed Jun 12 15:23:10 CDT 2013.
I'm getting this:
# portupgrade -a
make: Mk/Mk/bsd.port.mk line 1638: warning: Couldn't read shell's
output for if /sbin/sysctl -n
On Sun, 23 Jun 2013, Ruslan Bukin wrote:
On Sun, Jun 23, 2013 at 07:50:40PM +0300, Konstantin Belousov wrote:
On Sun, Jun 23, 2013 at 08:44:25PM +0400, Ruslan Bukin wrote:
On Sun, Jun 23, 2013 at 07:16:17PM +0300, Konstantin Belousov wrote:
On Sun, Jun 23, 2013 at 06:43:46PM +0400, Ruslan
13 matches
Mail list logo
