TB --- 2009-09-26 15:45:35 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2009-09-26 15:45:35 - starting RELENG_8 tinderbox run for ia64/ia64
TB --- 2009-09-26 15:45:36 - cleaning the object tree
TB --- 2009-09-26 15:48:08 - cvsupping the source tree
TB --- 2009-09-26 15:48:08 -
Hello everyone,
the discussion in -current and the behavior of my hard disk caused me to
investigate. Whenever kde programs are run on this system, the hard disk
will not spin down (even when excessive timeouts for syncs are in effect)
So I ran truss against kwallet and plasma-desktop to find
pro bono publico
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
I've got a couple FreeBSD 7.0 systems which I am trying to upgrade. I
had used ZFS for everything except the boot where I had used a gmirror.
I didn't really understand it all then, but it's been working fine.
The problem is that now with I make buildworld and make
installkernel I get the old
Daniel O'Connor wrote:
On Sat, 26 Sep 2009, Alan Cox wrote:
John Baldwin wrote:
On Friday 25 September 2009 3:20:05 am Daniel O'Connor wrote:
On Thu, 24 Sep 2009, John Baldwin wrote:
Can you try this patch perhaps:
Index: sys/amd64/isa/isa_dma.c
Back in July, I asked the following on this list. I didn't get any replies.
I was running 7.2 at the time and the messages were coming up every
couple of minutes. Now I've upgraded to 8-RC1 and the same message is
coming out on the console every few seconds. The miss count limit is now
a sysctl
Am 26.09.2009 um 21:04 schrieb Chris Shenton:
PS: Current gmirror list output:
$ gmirror list
Geom name: boot
State: COMPLETE
Components: 1
^^^
There's your problem: your mirror consist of only ad6s1a. You need to
add ad4s1a using gmirror insert, or tell your BIOS to boot from
On Fri, 25 Sep 2009, Jamie Gritton wrote:
It seems to be NFS related. I think the null pointer in question is from
the export's anonymous credential. Try the patch below and see if it helps
(which I guess means run it overnight and see if it crashes again). I've
also patched a similar
