Hello,
Today morning I wanted to make and install a fresh /head to an USB key
for further distribution the usual way:
...
# make installworld DESTDIR=/mnt
# make installkernel DESTDIR=/mnt KERNCONF=GENERIC INSTALL_NODEBUG=t
# make distrib-dirs DESTDIR=/mnt
# make distribution DESTDIR=/mnt
'i
Motherboard: Intel DQ77KB, the latest BIOS & AMT fw.
both ethernet interfaces connected,
DHCP configured only the the first (managment) or only the second - the
same result:
after appr. 5 min ? AMT can't be accesed.
(Same result on a few such a PCs which we have about ten in lab)
FreeBSD:
9.1 a
I need to know the details on the hardware this is on, and was it working
on some previous
version of FreeBSD and broke in STABLE or what?
Jack
On Mon, May 13, 2013 at 2:44 PM, Kamil Czekirda wrote:
> Jack, do you have any ideas to resolve problem, on new Debian 7 and Ubuntu
> 13.10 AMT worki
Jack, do you have any ideas to resolve problem, on new Debian 7 and Ubuntu
13.10 AMT working fine.
2013/5/9 John Baldwin
> On Thursday, May 09, 2013 4:34:16 am Kamil Czekirda wrote:
> > Do you have any ideas to resolve the problem?
>
> I have no idea what part of e1000 common code deals with AM
On May 7, 2013, at 16:10, Dimitry Andric wrote:
> On 2013-05-07 16:01, Sergey Kandaurov wrote:
>> On 7 May 2013 17:21, Michael W. Lucas wrote:
> ...
>>> c++ -O2 -pipe
>>> -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include
>>> -I/usr/src/lib/clang/libllvmsupport/../../../contrib/
Hartmut Brandt wrote:
> On Sun, 12 May 2013, Rick Macklem wrote:
>
> RM>Hartmut Brandt wrote:
> RM>> Hi,
> RM>>
> RM>> I've updated one of my -current machines this week (previous
> update
> RM>> was in
> RM>> february). Now I see a strange effect (it seems only on NFS
> mounts):
> RM>> ls or
> RM
On May 13, 2013, at 21:26, Anton Shterenlikht wrote:
> # uname -a
> FreeBSD mech-aslap239.men.bris.ac.uk 10.0-CURRENT FreeBSD 10.0-CURRENT #29
> r2463
> 70M: Tue Feb 19 09:04:48 GMT 2013
> r...@mech-aslap239.men.bris.ac.uk:/usr/obj
> /usr/src/sys/BUZI amd64
>
> make buildworld:
>
> c++ -
# uname -a
FreeBSD mech-aslap239.men.bris.ac.uk 10.0-CURRENT FreeBSD 10.0-CURRENT #29 r2463
70M: Tue Feb 19 09:04:48 GMT 2013 r...@mech-aslap239.men.bris.ac.uk:/usr/obj
/usr/src/sys/BUZI amd64
make buildworld:
c++ -O2 -pipe -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include
On 2013-05-13 13:20, Jung-uk Kim wrote:
How recent is your -CURRENT? FYI, recently we fixed couple of
auto-vectorization bugs, i.e.,
http://svnweb.freebsd.org/base?view=revision&revision=249817
http://svnweb.freebsd.org/base?view=revision&revision=250593
I have feeling that one of these might
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-05-11 05:25:41 -0400, O. Hartmann wrote:
> On Thu, 2013-05-09 at 17:16 -0500, Larry Rosenman wrote:
>> On 2013-05-09 06:16, Damjan Jovanovic wrote:
>>> On Wed, May 8, 2013 at 8:52 PM, Larry Rosenman
>>> wrote: On 2013-05-08 13:37, Larry Rosenm
On Mon, May 13, 2013 at 04:33:04PM +0200, Roger Pau Monn? wrote:
> On 13/05/13 13:18, Roger Pau Monn? wrote:
> > The VM can be stuck in this state for quite some time, it generally
>
> I would like to explain this a little bit more, the syncer process
> doesn't get blocked on the _mtx_trylock_flag
On 13/05/13 13:18, Roger Pau Monné wrote:
> The VM can be stuck in this state for quite some time, it generally
I would like to explain this a little bit more, the syncer process
doesn't get blocked on the _mtx_trylock_flags_ call, it just continues
looping forever in what seems to be an endless l
TB --- 2013-05-13 11:05:32 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-13 11:05:32 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-05-13 10:39:58 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-13 10:39:58 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-05-13 11:16:44 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-13 11:16:44 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-05-13 10:26:26 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-13 10:26:26 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
Hello,
I've set up a FreeBSD-HEAD VM on Xen, and compiled the XENHVM kernel,
last commit in the repository is:
Date: Tue, 7 May 2013 12:39:14 +
Subject: [PATCH] By request, add an arrow from NetBSD-0.8 to FreeBSD-1.0.
While here, add a few more NetBSD versions to the tree itself.
Submitted
TB --- 2013-05-13 10:13:53 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-13 10:13:53 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-05-13 08:20:35 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-05-13 08:20:35 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
On Sun, 12 May 2013, Rick Macklem wrote:
RM>Hartmut Brandt wrote:
RM>> Hi,
RM>>
RM>> I've updated one of my -current machines this week (previous update
RM>> was in
RM>> february). Now I see a strange effect (it seems only on NFS mounts):
RM>> ls or
RM>> even echo * will list only some files (str
20 matches
Mail list logo
