Philipp Wuensche wrote:
>
> It just now started running the kernel without IPSEC and ALTQ.
Here we go again, this time it crashed with IPSEC and ALTQ disabled,
crashdump looks different this time though.
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software,
Oops, the patch had a small mistake.
I've put it here now, just in case I'll want to fix/cleanup anything else:
http://people.freebsd.org/~avg/intel-cpu-topo.diff
on 28/08/2010 23:22 Andriy Gapon said the following:
> So, here is my take on the problem.
> The attached patch is against sources in
on 28/08/2010 01:02 Andriy Gapon said the following:
> BTW, it may be not that hard.
> It seems that 0x4 topology building involves knowing the masks and we already
> have that data (just interpreted differently), and APIC IDs of the CPUs and it
> seems that we also have that. We don't need to bin
This this something to be concerned about:
ACPI Warning: Optional field Pm2ControlBlock has zero address or length:
0x/0x1 (20100331/tbfadt-655)
--
Dan Langille - http://langille.org/
___
freebsd-stable@freebsd.org mailing list
http:/
On Sat, Aug 28, 2010 at 04:35:58PM -0400, Dan Langille wrote:
> This this something to be concerned about:
>
> ACPI Warning: Optional field Pm2ControlBlock has zero address or
> length: 0x/0x1 (20100331/tbfadt-655)
CC'ing freebsd-acpi. OS version is unknown.
--
| Jeremy Chadwic
On 8/28/2010 8:30 PM, Jeremy Chadwick wrote:
On Sat, Aug 28, 2010 at 04:35:58PM -0400, Dan Langille wrote:
This this something to be concerned about:
ACPI Warning: Optional field Pm2ControlBlock has zero address or
length: 0x/0x1 (20100331/tbfadt-655)
CC'ing freebsd-acpi. OS
Hi. I'm still having problems with NFSv4 being very laggy on one client.
When the NFSv4 server is at 50% idle CPU and the disks are < 1% busy, I am
getting horrible throughput on an idle client. Using dd(1) with 1 MB block
size, when I try to read a > 100 MB file from the client, I'm getting
arou
