During the reboot, immediately after the daemons started up on the
machine (the boot got beyond mounting all the disks and was well into
starting up all the background stuff it runs), I got a double-fault.
. (there were a LOT more of this same; it pretty clearly was a
recursive call sequence t
[image: Inline image 1]
Please reply to this email if you want to unsubscribe.
Best Regards
*Mousumi Nandan *
SARA | Business Development Executive
Mobile: +91 987 45678 47
Office: +91 33 400 88 333
Email: mousumi.sarainternatio...@gmail.com
sales.sarainternatio...@gmail.com
A second attempt to come up on the new kernel was successful -- so this
had to be due to queued I/Os that were pending at the time of the
shutdown
On 1/11/2017 08:31, Karl Denninger wrote:
> During the reboot, immediately after the daemons started up on the
> machine (the boot got beyond moun
-Original Message-From: David Boyd
To: freebsd-stable@freebsd.org
Subject: Regression in pciconf utility in releng/11.0
Date: Wed, 28 Dec 2016 10:14:57 -0500
pciconf -lv em0@pci0:6:0:0: returns the following error:
pciconf: cannont parse selector em0:pci0:6:0:0:
This is contrary
Hi,
I'm in the process of transferring my home server to an Intel NUC. I've zfs
send/receive'd the whole pool to the new drive and first followed
[ZfsOnGpt] but it fails in the first stage boot loader. The USB keyboard
doesn't seem to be recognized so I can't really debug anything.
Then I tried b
As your not at the boot loader stage yet for keyboard enabling legacy
USB keyboard / mouse support in BIOS may help.
If you see issues with keyboard after the kernel takes over setting
hint.ehci.0.disabled=1 may help.
If your installing 11.x then the guides boot partition size is out of
date
After today's OpenSSH security message, I did:
cd /usr
rm -rf obj
cd src
svn update -r311916
make buildworld
After a while, I got to:
building shared library libc.so.7
cc (a very long compile line)
./libc.so.7: unsupported file layout
*** Error code 1
Stop.
make[4]: stopped in /usr/src/lib/libc
On Wed, Jan 11, 2017 at 12:24 PM, George Mitchell
wrote:
> After today's OpenSSH security message, I did:
>
> cd /usr
> rm -rf obj
> cd src
> svn update -r311916
> make buildworld
>
> After a while, I got to:
>
> building shared library libc.so.7
> cc (a very long compile line)
> ./libc.so.7: uns
On 11 Jan 2017, at 21:24, George Mitchell wrote:
>
> After today's OpenSSH security message, I did:
>
> cd /usr
> rm -rf obj
Hmm, not sure if it is wise to completely remove the /usr/obj directory.
Did you re-create it afterwards?
> cd src
> svn update -r311916
> make buildworld
>
> After a
On 01/11/17 17:25, Dimitry Andric wrote:
> On 11 Jan 2017, at 21:24, George Mitchell wrote:
>>
>> After today's OpenSSH security message, I did:
>>
>> cd /usr
>> rm -rf obj
>
> Hmm, not sure if it is wise to completely remove the /usr/obj directory.
> Did you re-create it afterwards?
In the past
On 11 Jan 2017, at 23:35, George Mitchell wrote:
>
> On 01/11/17 17:25, Dimitry Andric wrote:
>> On 11 Jan 2017, at 21:24, George Mitchell wrote:
...
>>> building shared library libc.so.7
>>> cc (a very long compile line)
>>> ./libc.so.7: unsupported file layout
>>
>> If things went correctly,
On 01/11/17 17:20, Kevin Oberman wrote:
> [...]
>
> While I have no suggestions about the error building libc, your statement
> that you can't use freebsd-update due to your use of a custom kernel is
> incorrect. This is a common misconception and, in cases of very limited
> disk space, may be tru
On 01/11/17 17:40, Dimitry Andric wrote:
> On 11 Jan 2017, at 23:35, George Mitchell wrote:
>>
>> On 01/11/17 17:25, Dimitry Andric wrote:
>>> On 11 Jan 2017, at 21:24, George Mitchell wrote:
> ...
building shared library libc.so.7
cc (a very long compile line)
./libc.so.7: unsuppo
(Sorry I had to copy-paste this email from the archives to a new
thread, because I'm not subscribed to -stable@. Would you mind cc:ing
me next time please?)
> As your not at the boot loader stage yet for keyboard enabling legacy
> USB keyboard / mouse support in BIOS may help.
That worked, thanks
I inherited a lab that has a few hundred hosts running FreeBSD 7.2.
These hosts run test scripts that access files that are stored on
FreeBSD 6.3 host. The 6.3 host exports a /data directory with NFS
On the 7.2 hosts, I can see the exported directory:
$ showmount -e 6.3-host
Exports list on 6.3
On 11/01/2017 22:58, Jeremie Le Hen wrote:
(Sorry I had to copy-paste this email from the archives to a new
thread, because I'm not subscribed to -stable@. Would you mind cc:ing
me next time please?)
As your not at the boot loader stage yet for keyboard enabling legacy
USB keyboard / mouse supp
On 01/11/17 15:24, George Mitchell wrote:
> After today's OpenSSH security message, I did:
>
> cd /usr
> rm -rf obj
> cd src
> svn update -r311916
> make buildworld
>
> After a while, I got to:
>
> building shared library libc.so.7
> cc (a very long compile line)
> ./libc.so.7: unsupported file
On 01/11/17 17:46, George Mitchell wrote:
> On 01/11/17 17:20, Kevin Oberman wrote:
>> [...]
>>
>> While I have no suggestions about the error building libc, your statement
>> that you can't use freebsd-update due to your use of a custom kernel is
>> incorrect. This is a common misconception and, i
On Wed, Jan 11, 2017 at 8:24 PM, George Mitchell
wrote:
> On 01/11/17 17:46, George Mitchell wrote:
> > On 01/11/17 17:20, Kevin Oberman wrote:
> >> [...]
> >>
> >> While I have no suggestions about the error building libc, your
> statement
> >> that you can't use freebsd-update due to your use o
> On 12 Jan 2017, at 1:47 AM, Karl Young wrote:
>
> I inherited a lab that has a few hundred hosts running FreeBSD 7.2.
> These hosts run test scripts that access files that are stored on
> FreeBSD 6.3 host. The 6.3 host exports a /data directory with NFS
>
>
> On the 7.2 hosts, I can see the
20 matches
Mail list logo
