Re: panic with tcp timers

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

Re: panic with tcp timers

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

Re: panic with tcp timers

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 ___

Re: "_secure_path: cannot stat /etc/login.conf: Not permitted in capability mode"

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

Re: BBB (cpsw(4)) seems to be broken in the latest 11-current

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

11.0-ALPHA4 and VIMAGE

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

console in 11.0-ALPHA4

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

Re: 11.0-ALPHA4 and VIMAGE

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

Re: console in 11.0-ALPHA4

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

Re: Compiling 11 on a Raspberry B+ 2 failes [not in my experience for -r301975]

On 2016-Jun-19, at 7:41 PM, Mark Millard wrote: > Quoting Erich Dollansky erichsfreebsdlist at alogt.com Sun Jun 19 23:38:56 > UTC 2016 : > >> I am trying to compile HEAD on a Raspberry and get always the following >> error. >> >> Of course, compiling revision 302017 on amd64 works. >> >>

Re: panic with tcp timers

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>

Re: panic with tcp timers

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> > -

Re: panic with tcp timers

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

Re: panic with tcp timers

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>

Re: panic with tcp timers

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=ignore-most What are the old paths impacted? Hi Gleb, Digging through my

"_secure_path: cannot stat /etc/login.conf: Not permitted in capability mode"

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

Re: Virtualbox kernel module on 11-CURRENT

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

Re: panic with tcp timers

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> > >

Re: console in 11.0-ALPHA4

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

Re: panic with tcp timers

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. >

Re: console in 11.0-ALPHA4

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

Re: Samba 4.3 and 4.4 crashes on FreeBSD 11-ALPHA4

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

Re: panic with tcp timers

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>

Re: panic with tcp timers

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

Re: Samba 4.3 and 4.4 crashes on FreeBSD 11-ALPHA4

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

Re: console in 11.0-ALPHA4

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

Re: console in 11.0-ALPHA4

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

Re: console in 11.0-ALPHA4

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

Re: BBB (cpsw(4)) seems to be broken in the latest 11-current

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 > >

Re: console in 11.0-ALPHA4

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

Re: console in 11.0-ALPHA4

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

Call for 2016Q2 quarterly status reports

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

Re: console in 11.0-ALPHA4

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:

Re: console in 11.0-ALPHA4

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,

Re: (beagleboneblack/urtwn) Kernel page fault with the following non-sleepable locks held

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

Re: console in 11.0-ALPHA4

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

FYI: how long for a "nothing new" 11.0 -r301975 WITH_META_MODE=yes build on an rpi2?

[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

Re: Reproducible igb related panic 11.0-ALPHA4

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

Re: BBB (cpsw(4)) seems to be broken in the latest 11-current

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.

Re: Reproducible igb related panic 11.0-ALPHA4

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

Re: BBB (cpsw(4)) seems to be broken in the latest 11-current

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: >>

Re: console in 11.0-ALPHA4

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