After clean install, I pkg install these packages:
vim, irssi, tmux, zh-auto-tw-l10n, docproj, sudo, asciidoc,
source-highlight, intel-backlight
http://imgur.com/kZbfTS5
During install process, I got "Cannot solve problem using SAT solver,
trying another plan"
http://imgur.com/nMnwumv
Finally,
For what it's worth: my two biggest grievances with the vt(4) vs. sc(4) is
the unordered updates in the graphics mode which makes watching quickly
scrolling text on something like virtual machine console funky and lack of
support in the libvgl(3). The latter I find particularly hard to explain,
sin
On Mon, 20 Jun 2016 16:22:53 -0700 John Baldwin wrote
> On Monday, June 20, 2016 04:54:11 PM Ernie Luzar wrote:
> > Ed Maste wrote:
> > > On 20 June 2016 at 14:29, Ernie Luzar wrote:
> > >> I found the cause of this boot time message
> > >> "vicontrol: setting cursor type: Inappropriate ioctl fo
On Mon, Jun 20, 2016 at 6:01 PM, Ernie Luzar wrote:
> John Baldwin wrote:
>
>> On Monday, June 20, 2016 04:54:11 PM Ernie Luzar wrote:
>>
>>> Ed Maste wrote:
>>>
On 20 June 2016 at 14:29, Ernie Luzar wrote:
> I found the cause of this boot time message
> "vicontrol: setting cur
Dear FreeBSD Community,
The deadline for the next FreeBSD Quarterly Status update is July 7,
2016, for work done in April through June.
Status report submissions do not have to be very long. They may be about
anything happening in the FreeBSD project and community, and provide a
great way to inf
On 20 June 2016 at 23:22, John Baldwin wrote:
>
> There are tradeoffs in both directions. Neither console is a subset of the
> other. However, sc(4) is not really extendable to support the things it is
> missing. vt(4) is actively worked on, and patches for the features it lacks
> that you need
John Baldwin wrote:
On Monday, June 20, 2016 04:54:11 PM Ernie Luzar wrote:
Ed Maste wrote:
On 20 June 2016 at 14:29, Ernie Luzar wrote:
I found the cause of this boot time message
"vicontrol: setting cursor type: Inappropriate ioctl for device"
In my rc.conf I had this statement
vidcontrol
Em 19/06/2016 18:47, Otacílio escreveu:
Em 19/06/2016 18:40, Otacílio escreveu:
I was installing netperf on a fresh FreeBSD-ALPHA3
FreeBSD beaglebone 11.0-ALPHA3 FreeBSD 11.0-ALPHA3 #0 r301846: Mon
Jun 13 19:54:27 BRT 2016
ota@nostromo:/root/crochet/work/obj/arm.armv6/usr/src/sys/BEAGLEBONE-DE
On Monday, June 20, 2016 04:54:11 PM Ernie Luzar wrote:
> Ed Maste wrote:
> > On 20 June 2016 at 14:29, Ernie Luzar wrote:
> >> I found the cause of this boot time message
> >> "vicontrol: setting cursor type: Inappropriate ioctl for device"
> >>
> >> In my rc.conf I had this statement
> >> vidcon
Nice to hear. I am building it right now. Gotta get you some results in the
next few hours. Thanks!
-Max
On Mon, Jun 20, 2016 at 3:33 PM, Keith White wrote:
> On Mon, 20 Jun 2016, Luiz Otavio O Souza wrote:
>
> On Sun, Jun 19, 2016 at 1:11 AM, Maxim Sobolev wrote:
>>
>>> Jim, some update from h
On Mon, 20 Jun 2016, Luiz Otavio O Souza wrote:
On Sun, Jun 19, 2016 at 1:11 AM, Maxim Sobolev wrote:
Jim, some update from here. Running r283287 of the driver, I still see the
same "watchdog timeout" messages, but they do not lead to the interface
lockout. The traffic resumes momentarily. Whic
On 2016-06-20 18:18, Richard Perini wrote:
On Mon, Jun 20, 2016 at 02:54:30PM +1000, Richard Perini wrote:
Reproducible igb related panic 11.0-ALPHA4
OS: FreeBSD 11.0-ALPHA4 #6 r302022
Hardware: Asus P9D C224
(integrated
Submitted as PR 210417
--R
___
On Mon, Jun 20, 2016 at 02:54:30PM +1000, Richard Perini wrote:
>
> Reproducible igb related panic 11.0-ALPHA4
>
> OS: FreeBSD 11.0-ALPHA4 #6 r302022
> Hardware: Asus P9D C224
> (integrated
>
> Hi,
>
> Kernel panics within a few seconds with heavy network load. Using
> "iperf -c anot
Ed Maste wrote:
On 20 June 2016 at 14:29, Ernie Luzar wrote:
I found the cause of this boot time message
"vicontrol: setting cursor type: Inappropriate ioctl for device"
In my rc.conf I had this statement
vidcontrol -c blink -h 250
From testing it seems that vt does not handle the "blink" opti
On 20 June 2016 at 14:29, Ernie Luzar wrote:
>
> I found the cause of this boot time message
> "vicontrol: setting cursor type: Inappropriate ioctl for device"
>
> In my rc.conf I had this statement
> vidcontrol -c blink -h 250
> From testing it seems that vt does not handle the "blink" option for
On Jun 18, 2016, at 2:50 AM, Maxim Sobolev wrote:
> Updated my BBB to the latest -current, immediately got this while trying to
> make world over ssh console:
>
> 06:02:17 CPSW watchdog cpswss0: watchdog timeout
> cpswss0: Unable to cleanly shutdown transmitter
>
> Interface seems to be locked
On 20 June 2016 at 12:45, Trond Endrestøl
wrote:
>
> If you want textmode like in the old days, add this line to
> /boot/loader.conf:
>
> hw.vga.textmode="1"
One note, in textmode vt(4) is limited to cp437. The console still
uses Unicode internally but has a fixed lookup table to map to the
cp437
Trond Endrestøl wrote:
On Mon, 20 Jun 2016 11:36-0400, Ernie Luzar wrote:
I have installed 11.0-ALPHA4-i386-20160617-r301975.
The console looks very different from all previous releases.
I find it to be harder to read. This manifests it self with the boot log
messages and the normal behavior o
Hi,
On 6/20/16 11:58 AM, Gleb Smirnoff wrote:
> On Mon, Jun 20, 2016 at 11:55:55AM +0200, Julien Charbon wrote:
> J> > On Fri, Jun 17, 2016 at 11:27:39AM +0200, Julien Charbon wrote:
> J> > J> > Comparing stable/10 and head, I see two changes that could
> J> > J> > affect that:
> J> > J> >
> J>
Hi,
On 6/20/16 12:30 PM, Gleb Smirnoff wrote:
> On Mon, Jun 20, 2016 at 12:14:18PM +0200, Hans Petter Selasky wrote:
> H> On 06/20/16 11:58, Gleb Smirnoff wrote:
> H> > The fix I am working on now is doing exactly that. callout_reset must
> H> > return 0 if the callout is currently running.
> H>
On Mon, 20 Jun 2016 11:36-0400, Ernie Luzar wrote:
> I have installed 11.0-ALPHA4-i386-20160617-r301975.
>
> The console looks very different from all previous releases.
> I find it to be harder to read. This manifests it self with the boot log
> messages and the normal behavior of the virtual co
On Monday, June 20, 2016 11:36:09 AM Ernie Luzar wrote:
> I have installed 11.0-ALPHA4-i386-20160617-r301975.
>
> The console looks very different from all previous releases.
> I find it to be harder to read. This manifests it self with the boot log
> messages and the normal behavior of the virtua
On Sun, Jun 19, 2016 at 1:11 AM, Maxim Sobolev wrote:
> Jim, some update from here. Running r283287 of the driver, I still see the
> same "watchdog timeout" messages, but they do not lead to the interface
> lockout. The traffic resumes momentarily. Which is probably why I never paid
> much attentio
Hi,
On 20 Jun 2016, at 15:37, Ernie Luzar wrote:
Hello list;
I have installed 11.0-ALPHA4-i386-20160617-r301975 to test VIMAGE.
I have read previous list posts saying vimage was going to be part of
the base system in 11.0. When I configure a jail with vnet I get a
error typical of vimage not
Hello list;
I have installed 11.0-ALPHA4-i386-20160617-r301975 to test VIMAGE.
I have read previous list posts saying vimage was going to be part of
the base system in 11.0. When I configure a jail with vnet I get a
error typical of vimage not being compiled into the kernel.
To me it looks like
I have installed 11.0-ALPHA4-i386-20160617-r301975.
The console looks very different from all previous releases.
I find it to be harder to read. This manifests it self with the boot log
messages and the normal behavior of the virtual consoles.
But the real problem is in the notable hesitation wh
There's implications for RSS with how the callout system currently works.
If you don't know the RSS bucket ID of a connection in advance, you'll
create callouts on the wrong CPUs and then they're not migrated.
The initial work here did convert things over, but didn't place the
callouts in the rig
On Mon, Jun 20, 2016 at 04:42:39AM -0700, David Wolfskill wrote:
> After updating my (amd64) build machine from r302018 to r302026, things
> work OK, but (now that I've re-connected the serial cable so I can
> actually interact with the serial console -- i.e., this may have
> occurred a while back,
After updating my (amd64) build machine from r302018 to r302026, things
work OK, but (now that I've re-connected the serial cable so I can
actually interact with the serial console -- i.e., this may have
occurred a while back, but I wouldn't have noticed), I see:
...
Starting devd.
add host 127.0.
On 8/06/2016 5:13 AM, Kevin Oberman wrote:
On Tue, Jun 7, 2016 at 1:04 AM, Guido Falsi wrote:
On 06/07/16 02:23, Rafael Rodrigues Nakano wrote:
Hello,
I tried installing virtualbox from packages, building it from sources,
trying the GENERIC kernel but everytime I can't start the kernel modul
On 06/20/16 12:30, Gleb Smirnoff wrote:
What does prevent us from converting TCP timeouts to locked? To my
understanding it is the lock order of taking pcbinfo after pcb lock.
I started this work:
https://reviews.freebsd.org/D1563
--HPS
___
freebsd-
On 06/20/16 12:30, Gleb Smirnoff wrote:
Exactly! I am convinced that all callouts should be locked, and non-locked
one should simply go away, as well as async drain.
I agree about that that, except you still need the async drain, because
it will prevent freeing the lock protecting the callout,
On Mon, Jun 20, 2016 at 11:55:55AM +0200, Julien Charbon wrote:
>
> Hi,
>
> On 6/20/16 9:39 AM, Gleb Smirnoff wrote:
> > On Fri, Jun 17, 2016 at 11:27:39AM +0200, Julien Charbon wrote:
> > J> > Comparing stable/10 and head, I see two changes that could
> > J> > affect that:
> > J> >
> > J> > -
On 06/20/16 11:58, Gleb Smirnoff wrote:
J> callout_stop() should return 0 when the callout is currently being
J> serviced and indeed unstoppable
J>
https://reviews.freebsd.org/differential/changeset/?ref=62513&whitespace=ignore-most
What are the old paths impacted?
Hi Gleb,
Digging throu
On Mon, Jun 20, 2016 at 12:14:18PM +0200, Hans Petter Selasky wrote:
H> On 06/20/16 11:58, Gleb Smirnoff wrote:
H> > The fix I am working on now is doing exactly that. callout_reset must
H> > return 0 if the callout is currently running.
H> >
H> > What are the old paths impacted?
H>
H> Hi,
H>
H>
On 06/20/16 11:58, Gleb Smirnoff wrote:
The fix I am working on now is doing exactly that. callout_reset must
return 0 if the callout is currently running.
What are the old paths impacted?
Hi,
I'll dig into the matter aswell and give some comments. Thanks for the
analysis, Gleb.
FYI: This
On Mon, Jun 20, 2016 at 11:30:38AM +0200, Daniel Engberg wrote:
> On 2016-06-19 11:17, Konstantin Belousov wrote:
> > On Sun, Jun 19, 2016 at 11:09:02AM +0200, Daniel Engberg wrote:
> >> I have the following in /etc/src.conf
> >>
> >> MALLOC_PRODUCTION=yes
> >> WITHOUT_DEBUG_FILES=1
> >
> > Most i
On Mon, Jun 20, 2016 at 11:55:55AM +0200, Julien Charbon wrote:
J> > On Fri, Jun 17, 2016 at 11:27:39AM +0200, Julien Charbon wrote:
J> > J> > Comparing stable/10 and head, I see two changes that could
J> > J> > affect that:
J> > J> >
J> > J> > - callout_async_drain
J> > J> > - switch to READ lock
Hi,
On 6/20/16 9:39 AM, Gleb Smirnoff wrote:
> On Fri, Jun 17, 2016 at 11:27:39AM +0200, Julien Charbon wrote:
> J> > Comparing stable/10 and head, I see two changes that could
> J> > affect that:
> J> >
> J> > - callout_async_drain
> J> > - switch to READ lock for inp info in tcp timers
> J> >
On 2016-06-19 11:17, Konstantin Belousov wrote:
> On Sun, Jun 19, 2016 at 11:09:02AM +0200, Daniel Engberg wrote:
>> I have the following in /etc/src.conf
>>
>> MALLOC_PRODUCTION=yes
>> WITHOUT_DEBUG_FILES=1
>
> Most important is to remove WITHOUT_DEBUG_FILES and recompile the world.
>
Hi,
My l
[One oddity of the rpi2 context for the below is that the root file system is
on a fast USB SSD drive: it is really a fast USB 3.0 SSD drive just used on the
USB 2 bus via a USB 3.0 capable hub.]
I just did the following sort of sequence on an rpi2 for 11.0 -r301975
rebuilding itself where the
Hi!
On Fri, Jun 17, 2016 at 11:27:39AM +0200, Julien Charbon wrote:
J> > Comparing stable/10 and head, I see two changes that could
J> > affect that:
J> >
J> > - callout_async_drain
J> > - switch to READ lock for inp info in tcp timers
J> >
J> > That's why you are in To, Julien and Hans :)
J>
42 matches
Mail list logo
