Re: Filesystem operations slower in 13.0 than 12.2

[Kevin Oberman]

On Mon, Mar 22, 2021 at 8:19 AM Adrian Chadd  wrote:

> On Mon, 15 Mar 2021 at 14:58, Kevin Oberman  wrote:
>
> > >
> > > It appears that the messages are associated with reading
> > > the disk(s), not directly with writing them, where the
> > > reads take more than "hz * 20" time units to complete.
> > > (I'm looking at main (14) code.) What might contribute
> > > to the time taken for the pending read(s)?
> > >
> > The reference to hz * 20 woke up a few sleeping memory cells. I forgot
> that
> > I cleaned up my loader.conf. It was largely a copy of the one on my
> > decade-old T520. I commented out "kern.hz=100". I don't recall the
> details,
> > but I think it was actually from an even older system, my T42 from
> before I
> > retired.
> >
> > In any case, restoring this setting has greatly improved the situation. I
> > now have really bad disk I/O performance on large disk to disk activity
> > (untarring the firefox distro) instead of terrible performance and the
> > system freezes have vanished, though I do see pauses in response to
> clicks
> > or text entry, but the display remains active and the pauses are
> short... 1
> > to 15 seconds, I'd guess. No, I have no idea what this indicates.
>
> ... which drive controller is this? Is it just a laptop ATA disk?
>
> > I'm still not seeing the performance I was seeing back in February when
> 40
> > MB/s for extended intervals was common and I once untarred
> firefox.tar.gz2
> > in under a minute and performance seldom dropped below 1.4 MB/s.
>
> Did you find a resolution?  I wonder if setting kern.hz is kicking
> some process(es) to get some time more frequently due to bugs
> elsewhere in the system (interrupts, IPI handling, wake-ups, etc)
>
>
>
> -adrian
>
No resolution. This is a Lenovo L15 ThinkPad with a 2TB ATAPI drive. The
current drive is a Seagate.  All testing has been done since I got it back
from Lenovo in late January. I can read or write the drive at reasonable
rates that exceed 50 MB/s. Extracting a tar distribution file is painful. I
have had firefox extracts take over a half hour. Worse, if I do other
operations while the extract is taking place, I often see a 30 second (and,
occasionally 60 second) display freezes as well as log reports that of
"swap_pager: indefinite wait buffer:" This is a bit odd as I have 20G of
RAM and am pretty close to no swap space activity, but, of course, paging
does occur.

This system is CometLake and graphics are not supported on 12. I am not
absolutely sure that there is not a hardware issue even though the main
board, the disk, and the keyboard/mouse pad have all been replace since I
received the system back last June. I now wonder what else could go wrong.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: ThinkPad X1 Carbon Gen 4 unable to boot 13.0-RC1

[Kevin Oberman]

On Sat, Mar 20, 2021 at 8:35 AM Fred via freebsd-stable <
freebsd-stable@freebsd.org> wrote:

> On 3/19/21 7:59 PM, Mathias Picker wrote:
> >
> > Fred Hall via freebsd-stable  writes:
> >
> >> I have a ThinkPad X1 Carbon Gen 4 (20FCS0NB00) which has happily run
> >> FreeBSD 11 and 12, but which can't boot 13.0-RC1 from memstick or via
> >> freebsd-update. In both cases the boot process locks up on the line
> >> "hwpstate_intel0:  on cpu0"
> >> If running freebsd-update, a work around is to add
> >> hint.hwpstate_intel.0.disabled="1" in loader.conf. See the note under
> >> the Eighth Generation (2020) in
> >> https://wiki.freebsd.org/Laptops/Thinkpad_X1_Carbon
> >> I was quite surprised to find the lack of support for hwpstate_intel
> >> in 13 when it apparently worked under 11 and 12. Does anyone know the
> >> status of hwpstate_intel on ThinkPads?
> >
> > I’m running 13 -STABLE from 10 days ago on a Thinkpad Yoga 3rd gen, and
> > hwpstate_intel works fine, never had a problem.
> >
> > mathiasp:~% sysctl dev.hwpstate_intel dev.hwpstate_intel.7.epp: 15
> > dev.hwpstate_intel.7.%parent: cpu7
> > dev.hwpstate_intel.7.%pnpinfo: dev.hwpstate_intel.7.%location:
> > dev.hwpstate_intel.7.%driver: hwpstate_intel
> > dev.hwpstate_intel.7.%desc: Intel Speed Shift
> > dev.hwpstate_intel.6.epp: 15
> > dev.hwpstate_intel.6.%parent: cpu6
> > dev.hwpstate_intel.6.%pnpinfo: dev.hwpstate_intel.6.%location:
> > dev.hwpstate_intel.6.%driver: hwpstate_intel
> > dev.hwpstate_intel.6.%desc: Intel Speed Shift
> > [snip]
> >
> > The gen3 is using
> > sudo dmesg|grep -i cpu
> > CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (1992.08-MHz K8-class CPU)
> > [snip, snip]
> >
> > mathiasp:~% uname -a
> > FreeBSD Danton 13.0-STABLE FreeBSD 13.0-STABLE #2
> > stable/13-n244845-f21c0366f53: Wed Mar 10 20:53:26 CET 2021
> > root@Danton:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64
> >
> >
> > Cheers,
> >
> > Mathias
>
> Thanks for the feed back. Good to know most people won't encounter the
> problem. Perhaps it is a bios issue specific to the model. I did update
> to the latest bios version but that made no difference.
>
> I have chosen to rollback to 12.2 as it works perfectly for me.
>
> >
> >> Cheers, Fred
>
There are two long tickets about this. Take a look at tickets 248659
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248659> and 253288
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253288>. This problem
appeared in 13-current in Jan 2020 and I first saw it on my new Lenovo L15
that summer. It appears specific to Lenovo laptops. It appears that similar
issues have been seen with Linux.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Filesystem operations slower in 13.0 than 12.2

[Kevin Oberman]

Responses in-line.

On Sun, Mar 14, 2021 at 3:09 PM Mark Millard  wrote:

>
>
> On 2021-Mar-14, at 11:09, Kevin Oberman  wrote:
>
> > . . .
> >
> > Seems to only occur on large r/w operations from/to the same disk. "sp
> > big-file /other/file/on/same/disk" or tar/untar operations on large
> files.
> > Hit this today updating firefox.
> >
> > I/O starts at >40MB/s. Dropped to about 1.5MB/s. If I tried doing other
> > things while it was running slowly, the disk would appear to lock up.
> E.g.
> > pwd(1) seemed to completely lock up the system, but I could still ping it
> > and, after about 30 seconds, things came back to life. It was also not
> > instantaneous. Disc activity dropped to <1MB/s for a few seconds before
> > everything froze.
> >
> > During the untar of firefox, I saw; this several times. I also looked at
> my
> > console where I found these errors during :
> > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 55043, size: 8192
> > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 51572, size: 4096
>
> Does anyone know:
> Are those messages normal "reading is taking a rather long
> time" notices or is their presence more useful information
> in some way about the type of problem or context for the
> problem?
>
> As for the tests:
> Are these messages always present when near a time frame
> when the problem occurs? Never present in a near time
> frame to a period when the problem does not occur?
>
In a large number of test, these errors have not repeated. They baffle me
for another reason. This system has 20G or RAM. Tyically, all swap space is
unused. ATM I see 16384M free out of 16384. Not sure that I have ever seen
it used, though it might have been while building rust. I have not built
rust for a month.

>
> It appears that the messages are associated with reading
> the disk(s), not directly with writing them, where the
> reads take more than "hz * 20" time units to complete.
> (I'm looking at main (14) code.) What might contribute
> to the time taken for the pending read(s)?
>
The reference to hz * 20 woke up a few sleeping memory cells. I forgot that
I cleaned up my loader.conf. It was largely a copy of the one on my
decade-old T520. I commented out "kern.hz=100". I don't recall the details,
but I think it was actually from an even older system, my T42 from before I
retired.

In any case, restoring this setting has greatly improved the situation. I
now have really bad disk I/O performance on large disk to disk activity
(untarring the firefox distro) instead of terrible performance and the
system freezes have vanished, though I do see pauses in response to clicks
or text entry, but the display remains active and the pauses are short... 1
to 15 seconds, I'd guess. No, I have no idea what this indicates.

I'm still not seeing the performance I was seeing back in February when 40
MB/s for extended intervals was common and I once untarred firefox.tar.gz2
in under a minute and performance seldom dropped below 1.4 MB/s.


>
> /*
>  * swap_pager_getpages() - bring pages in from swap
>  *
>  *  Attempt to page in the pages in array "ma" of length "count".  The
>  *  caller may optionally specify that additional pages preceding and
>  *  succeeding the specified range be paged in.  The number of such
> pages
>  *  is returned in the "rbehind" and "rahead" parameters, and they will
>  *  be in the inactive queue upon return.
>  *
>  *  The pages in "ma" must be busied and will remain busied upon
> return.
>  */
> static int
> swap_pager_getpages_locked(vm_object_t object, vm_page_t *ma, int count,
> int *rbehind, int *rahead)
> {
> . . .
> /*
>  * Wait for the pages we want to complete.  VPO_SWAPINPROG is
> always
>  * cleared on completion.  If an I/O error occurs, SWAPBLK_NONE
>  * is set in the metadata for each page in the request.
>  */
> VM_OBJECT_WLOCK(object);
> /* This could be implemented more efficiently with aflags */
> while ((ma[0]->oflags & VPO_SWAPINPROG) != 0) {
> ma[0]->oflags |= VPO_SWAPSLEEP;
> VM_CNT_INC(v_intrans);
> if (VM_OBJECT_SLEEP(object, >handle, PSWP,
> "swread", hz * 20)) {
> printf(
> "swap_pager: indefinite wait buffer: bufobj: %p, blkno: %jd, size: %ld\n",
> bp->b_bufobj, (intmax_t)bp->b_blkno,
> bp->b_bcount);
> }
> }
> VM_OBJECT_WUNLOCK(object);
> . . .
>
> where:
>
> #defin

Re: Filesystem operations slower in 13.0 than 12.2

[Kevin Oberman]

On Sat, Mar 13, 2021 at 9:43 PM Kevin Oberman  wrote:

> No improvement with stable/13-n244880-cec3990d347.  It may be worse.
> worse. An attempt to unpack firefox-86.0.1,2 saw disk rates in the range
> of 800K to 2 MB/s range and with repeated 30 second freezes. I have no idea
> what made it so much worse, but I'm forced to start wondering if it could
> be a hardware issue. The disk drive was already replaced once due to a bad
> bearing. Went from a WD Black to a Seagate. Since it just keeps getting
> worse, I must consider that possibility. It is odd, though, that it was
> suddenly worse with the updated system.
>
> I think I will try going back to n244765-a00bf7d9bba (March 4) and see if
> it improves. If it does, I can likely eliminate bad hardware.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>
>
> On Sat, Mar 13, 2021 at 6:00 PM Warner Losh  wrote:
>
>>
>>
>> On Sat, Mar 13, 2021 at 6:37 PM Kevin Oberman 
>> wrote:
>>
>>> I have been dealing with this for a long time since head back in
>>> September through 13-stable of Mar-4. I have seen no improvement over this
>>> time. It seems (my perception without supporting data) that it got worse in
>>> the timeframe of BETA-3 tag. I was running stable, so not quite BETA-3. It
>>> also does not help that I have also been bitten by the P-State related
>>> freeze issue which has some similarities. disabling p-states has almost
>>> eliminated this issue, though, with only three occurrences since I disabled
>>> them in late January.
>>>
>>>  As a result, I don't think it is a recent change, but a problem that
>>> has existed for at least 3 months. This was made worse by two hardware
>>> issues that kept the system unavailable for most of the time between buying
>>> it last spring and getting the keyboard replaced in January. (Both the
>>> mainboard and the disk drive had already been replaced.)  There was another
>>> slow I/O issue that I had assumed was the same as mine, but was reportedly
>>> fixed with BETA-4. A few are still seeing slow I/O, so I assume that there
>>> were different issues with I/O. Since CometLake systems seem pretty
>>> uncommon, it might be related to that.
>>>
>>
>> It was a change from last fall, or set of changes. RC1 or defintely RC2
>> has fixes to regain performance lost. If BETA4 was the last one you
>> evaluated, perhaps you could do a couple tests with RC2 now that it's out
>> to see if it is the same thing?
>>
>> Warner
>>
>>
>>> Kevin Oberman, Part time kid herder and retired Network Engineer
>>> E-mail: rkober...@gmail.com
>>> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>>>
>>>
>>> On Sat, Mar 13, 2021 at 4:36 PM Warner Losh  wrote:
>>>
>>>>
>>>>
>>>> On Sat, Mar 13, 2021 at 5:33 PM Kevin Oberman 
>>>> wrote:
>>>>
>>>>> Just spent a little time looking at my issue and have a few more notes:
>>>>>
>>>>
>>>> What version did you evaluate? There's a number of changes lately that
>>>> could have a big impact on this...
>>>>
>>>> Warner
>>>>
>>>>
>>>>> Seems to only occur on large r/w operations from/to the same disk. "sp
>>>>> big-file /other/file/on/same/disk" or tar/untar operations on large
>>>>> files.
>>>>> Hit this today updating firefox.
>>>>>
>>>>> I/O starts at >40MB/s. Dropped to about 1.5MB/s. If I tried doing other
>>>>> things while it was running slowly, the disk would appear to lock up.
>>>>> E.g.
>>>>> pwd(1) seemed to completely lock up the system, but I could still ping
>>>>> it
>>>>> and, after about 30 seconds, things came back to life. It was also not
>>>>> instantaneous. Disc activity dropped to <1MB/s for a few seconds before
>>>>> everything froze.
>>>>>
>>>>> During the untar of firefox, I saw; this several times. I also looked
>>>>> at my
>>>>> console where I found these errors during :
>>>>> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 55043, size: 8192
>>>>> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 51572, size: 4096
>>>>>
>>>>> I should note that some operations continue just fine while 

Re: Filesystem operations slower in 13.0 than 12.2

[Kevin Oberman]

No improvement with stable/13-n244880-cec3990d347.  It may be worse. worse.
An attempt to unpack firefox-86.0.1,2 saw disk rates in the range of 800K
to 2 MB/s range and with repeated 30 second freezes. I have no idea what
made it so much worse, but I'm forced to start wondering if it could be a
hardware issue. The disk drive was already replaced once due to a bad
bearing. Went from a WD Black to a Seagate. Since it just keeps getting
worse, I must consider that possibility. It is odd, though, that it was
suddenly worse with the updated system.

I think I will try going back to n244765-a00bf7d9bba (March 4) and see if
it improves. If it does, I can likely eliminate bad hardware.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


On Sat, Mar 13, 2021 at 6:00 PM Warner Losh  wrote:

>
>
> On Sat, Mar 13, 2021 at 6:37 PM Kevin Oberman  wrote:
>
>> I have been dealing with this for a long time since head back in
>> September through 13-stable of Mar-4. I have seen no improvement over this
>> time. It seems (my perception without supporting data) that it got worse in
>> the timeframe of BETA-3 tag. I was running stable, so not quite BETA-3. It
>> also does not help that I have also been bitten by the P-State related
>> freeze issue which has some similarities. disabling p-states has almost
>> eliminated this issue, though, with only three occurrences since I disabled
>> them in late January.
>>
>>  As a result, I don't think it is a recent change, but a problem that has
>> existed for at least 3 months. This was made worse by two hardware issues
>> that kept the system unavailable for most of the time between buying it
>> last spring and getting the keyboard replaced in January. (Both the
>> mainboard and the disk drive had already been replaced.)  There was another
>> slow I/O issue that I had assumed was the same as mine, but was reportedly
>> fixed with BETA-4. A few are still seeing slow I/O, so I assume that there
>> were different issues with I/O. Since CometLake systems seem pretty
>> uncommon, it might be related to that.
>>
>
> It was a change from last fall, or set of changes. RC1 or defintely RC2
> has fixes to regain performance lost. If BETA4 was the last one you
> evaluated, perhaps you could do a couple tests with RC2 now that it's out
> to see if it is the same thing?
>
> Warner
>
>
>> Kevin Oberman, Part time kid herder and retired Network Engineer
>> E-mail: rkober...@gmail.com
>> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>>
>>
>> On Sat, Mar 13, 2021 at 4:36 PM Warner Losh  wrote:
>>
>>>
>>>
>>> On Sat, Mar 13, 2021 at 5:33 PM Kevin Oberman 
>>> wrote:
>>>
>>>> Just spent a little time looking at my issue and have a few more notes:
>>>>
>>>
>>> What version did you evaluate? There's a number of changes lately that
>>> could have a big impact on this...
>>>
>>> Warner
>>>
>>>
>>>> Seems to only occur on large r/w operations from/to the same disk. "sp
>>>> big-file /other/file/on/same/disk" or tar/untar operations on large
>>>> files.
>>>> Hit this today updating firefox.
>>>>
>>>> I/O starts at >40MB/s. Dropped to about 1.5MB/s. If I tried doing other
>>>> things while it was running slowly, the disk would appear to lock up.
>>>> E.g.
>>>> pwd(1) seemed to completely lock up the system, but I could still ping
>>>> it
>>>> and, after about 30 seconds, things came back to life. It was also not
>>>> instantaneous. Disc activity dropped to <1MB/s for a few seconds before
>>>> everything froze.
>>>>
>>>> During the untar of firefox, I saw; this several times. I also looked
>>>> at my
>>>> console where I found these errors during :
>>>> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 55043, size: 8192
>>>> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 51572, size: 4096
>>>>
>>>> I should note that some operations continue just fine while this is
>>>> going
>>>> on until I do something that freezes the system. I assume that this
>>>> eliminates the disk drive and low-level driver. Is vfs a possible
>>>> issue. It
>>>> had some serious work in the past few months by markj. That does not
>>>> explain why more people are not seeing this.
>>>>
>>>> I have been seeing this since at least

Re: Filesystem operations slower in 13.0 than 12.2

[Kevin Oberman]

I have been dealing with this for a long time since head back in September
through 13-stable of Mar-4. I have seen no improvement over this time. It
seems (my perception without supporting data) that it got worse in the
timeframe of BETA-3 tag. I was running stable, so not quite BETA-3. It also
does not help that I have also been bitten by the P-State related freeze
issue which has some similarities. disabling p-states has almost eliminated
this issue, though, with only three occurrences since I disabled them in
late January.

 As a result, I don't think it is a recent change, but a problem that has
existed for at least 3 months. This was made worse by two hardware issues
that kept the system unavailable for most of the time between buying it
last spring and getting the keyboard replaced in January. (Both the
mainboard and the disk drive had already been replaced.)  There was another
slow I/O issue that I had assumed was the same as mine, but was reportedly
fixed with BETA-4. A few are still seeing slow I/O, so I assume that there
were different issues with I/O. Since CometLake systems seem pretty
uncommon, it might be related to that.

Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


On Sat, Mar 13, 2021 at 4:36 PM Warner Losh  wrote:

>
>
> On Sat, Mar 13, 2021 at 5:33 PM Kevin Oberman  wrote:
>
>> Just spent a little time looking at my issue and have a few more notes:
>>
>
> What version did you evaluate? There's a number of changes lately that
> could have a big impact on this...
>
> Warner
>
>
>> Seems to only occur on large r/w operations from/to the same disk. "sp
>> big-file /other/file/on/same/disk" or tar/untar operations on large files.
>> Hit this today updating firefox.
>>
>> I/O starts at >40MB/s. Dropped to about 1.5MB/s. If I tried doing other
>> things while it was running slowly, the disk would appear to lock up. E.g.
>> pwd(1) seemed to completely lock up the system, but I could still ping it
>> and, after about 30 seconds, things came back to life. It was also not
>> instantaneous. Disc activity dropped to <1MB/s for a few seconds before
>> everything froze.
>>
>> During the untar of firefox, I saw; this several times. I also looked at
>> my
>> console where I found these errors during :
>> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 55043, size: 8192
>> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 51572, size: 4096
>>
>> I should note that some operations continue just fine while this is going
>> on until I do something that freezes the system. I assume that this
>> eliminates the disk drive and low-level driver. Is vfs a possible issue.
>> It
>> had some serious work in the past few months by markj. That does not
>> explain why more people are not seeing this.
>>
>> I have been seeing this since at least September 2020, so it goes back a
>> way. As this CometLake system will not run graphics on 12, I can't confirm
>> operation before 13.
>> --
>> Kevin Oberman, Part time kid herder and retired Network Engineer
>> E-mail: rkober...@gmail.com
>> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>>
>>
>> On Fri, Mar 5, 2021 at 10:47 PM Mark Millard via freebsd-stable <
>> freebsd-stable@freebsd.org> wrote:
>>
>> >
>> > Konstantin Belousov kostikbel at gmail.com wrote on
>> > Fri Mar 5 23:12:13 UTC 2021 :
>> >
>> > > On Sat, Mar 06, 2021 at 12:27:55AM +0200, Christos Chatzaras wrote:
>> > . . .
>> > > > Command: /usr/bin/time -l portsnap extract (these tests done with 2
>> > different idle servers but with same 4TB HDDs models)
>> > > >
>> > > > FreeBSD 12.2p4
>> > > >
>> > > >99.45 real34.90 user59.63 sys
>> > > >   100.00 real34.91 user59.97 sys
>> > > >82.95 real35.98 user60.68 sys
>> > > >
>> > > > FreeBSD 13.0-RC1
>> > > >
>> > > >   217.43 real75.67 user   110.97 sys
>> > > >   125.50 real63.00 user96.47 sys
>> > > >   118.93 real62.91 user96.28 sys
>> > > . . .
>> > > In the portsnap results for 13RC1, the variance is too high to
>> conclude
>> > > anything, I think.
>> >
>> > I'll note that there are other reports of wide variance
>> > in transfer rates observed during an overall operation
>> > such as "make ext

Re: Filesystem operations slower in 13.0 than 12.2

[Kevin Oberman]

Just spent a little time looking at my issue and have a few more notes:

Seems to only occur on large r/w operations from/to the same disk. "sp
big-file /other/file/on/same/disk" or tar/untar operations on large files.
Hit this today updating firefox.

I/O starts at >40MB/s. Dropped to about 1.5MB/s. If I tried doing other
things while it was running slowly, the disk would appear to lock up. E.g.
pwd(1) seemed to completely lock up the system, but I could still ping it
and, after about 30 seconds, things came back to life. It was also not
instantaneous. Disc activity dropped to <1MB/s for a few seconds before
everything froze.

During the untar of firefox, I saw; this several times. I also looked at my
console where I found these errors during :
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 55043, size: 8192
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 51572, size: 4096

I should note that some operations continue just fine while this is going
on until I do something that freezes the system. I assume that this
eliminates the disk drive and low-level driver. Is vfs a possible issue. It
had some serious work in the past few months by markj. That does not
explain why more people are not seeing this.

I have been seeing this since at least September 2020, so it goes back a
way. As this CometLake system will not run graphics on 12, I can't confirm
operation before 13.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


On Fri, Mar 5, 2021 at 10:47 PM Mark Millard via freebsd-stable <
freebsd-stable@freebsd.org> wrote:

>
> Konstantin Belousov kostikbel at gmail.com wrote on
> Fri Mar 5 23:12:13 UTC 2021 :
>
> > On Sat, Mar 06, 2021 at 12:27:55AM +0200, Christos Chatzaras wrote:
> . . .
> > > Command: /usr/bin/time -l portsnap extract (these tests done with 2
> different idle servers but with same 4TB HDDs models)
> > >
> > > FreeBSD 12.2p4
> > >
> > >99.45 real34.90 user59.63 sys
> > >   100.00 real34.91 user59.97 sys
> > >82.95 real35.98 user60.68 sys
> > >
> > > FreeBSD 13.0-RC1
> > >
> > >   217.43 real75.67 user   110.97 sys
> > >   125.50 real63.00 user96.47 sys
> > >   118.93 real62.91 user96.28 sys
> > . . .
> > In the portsnap results for 13RC1, the variance is too high to conclude
> > anything, I think.
>
> I'll note that there are other reports of wide variance
> in transfer rates observed during an overall operation
> such as "make extract". The one I'm thinking of is:
>
> https://lists.freebsd.org/pipermail/freebsd-stable/2021-March/093251.html
>
> which is an update to earlier reports, but based on more recent
> stable/13. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253968
> comment 4 has some more notes about the context. The "make extract"
> for firefox likely is not as complicated as the portsnap extract
> example's execution structure.
>
> Might be something to keep an eye on if there are on-going
> examples of over time.
>
> ===
> Mark Millard
> marklmi at yahoo.com
> ( dsl-only.net went
> away in early 2018-Mar)
>
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD 13.0-BETA2 and slow IO

[Kevin Oberman]

On Sun, Feb 28, 2021 at 12:49 PM Christos Chatzaras 
wrote:

> Did someone test if this is fixed in BETA4?
>

Just tried to "make extract" on firefox and I am still seeing transfer
rates around 1.7M when I would expect more like 50M. If I see the same
thing others are, it runs for a while at >40MB and abruptly drops to
1.5-20M for some random time varying from a few seconds to minutes before
jumping back to >40MB. Is this what others are seeing?
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683J
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: How do I know if my 13-stable has security patches?

[Kevin Oberman]

Well, back to a full clone. Thanks for the "--unshallow" argument, but so
far it has failed twice. I suspect that it's my urtwn interface is bad.
I'll swap it out tomorrow and see it that fixes it.

I am a bit surprised at how little more space the full clone takes. I was
really expecting it to be much worse. Of course, it will only grow... as
will the sources, themselves.

Warner, I suggest an immediate update to your mini-git primer. It was
already a bit out of date, but this fix is more urgent with RC on the
horizon. In particular, the "Repositories" at least look old to me.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


On Fri, Feb 26, 2021 at 10:55 AM Ed Maste  wrote:

> On Fri, 26 Feb 2021 at 12:10, Helge Oldach  wrote:
> >
> > A shallow tree is about 1.6G. If you want to patch source (say, from
> > a SA or EN) you certainly also need space for an object tree which is
> > about 4.5G. The total is >6G.
> >
> > I'd say relative to the total required to build, the 1.1G "savings" from
> > using a shallow versus a full tree (which is about 2.7G) isn't really
> > worth the effort. Plus, you get the a few benefits like full commit
> > history including comments.
>
> Indeed, this is a good point. We can update docs to state:
>
> At present a full clone is required to include the commit count in
> uname. An existing shallow clone can be converted into a full clone by
> running
>
> % git fetch --unshallow
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Drastic slowdown for geli attach

[Kevin Oberman]

On Thu, Feb 25, 2021 at 3:44 PM Ian Lepore  wrote:

> On Wed, 2021-02-24 at 21:34 -0800, Kevin Oberman wrote:
> > Sometime around the first week of this month (February) the time to
> > do a
> > geli attach on my 13.0-ALPHA3 amd64 system sharply increased. It
> > started
> > taking about 10 seconds. Prior to this, it took about 3-4 seconds. I
> > have
> > not seen any issues with the disc after it attaches, I am simply
> > concerned
> > that the longer time may be indicative of a deeper issue.
> >
> > The system is a ThinkPad L15 with a CometLake i5-10210U and a Seagate
> > ST2000LM007-1R8174 2T HDD.
> > --
> > Kevin Oberman, Part time kid herder and retired Network Engineer
> > E-mail: rkober...@gmail.com
> > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
> > ___
> > freebsd-stable@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "
> > freebsd-stable-unsubscr...@freebsd.org"
>
> In my experience, the thing that takes the most time in a geli attach
> is the iterations of PKCS#5v2 it performs.  When you setup geli on a
> partition it calculates how many iterations take about 2 seconds to
> perform (unless you provide a specific value with the -i flag).
>
> If you set up geli on a very fast machine then move the storage to a
> slower machine, it may take much longer than 2 seconds.  (And if you
> have 10 drives to attach, 2 seconds each becomes annoying, so I tend to
> use -i with a small-ish number like 5000).
>
> Or, in your case, maybe something has changed like it used to use aesni
> accellerated instructions and now it doesn't for some reason, like
> different default flags got used on the build, or something changed in
> the crypto and/or driver framework.  That's the kind of thing I'd be
> looking for.
>
> -- Ian
>
I think I see the cause. The filesystem was originally encrypted with geli
several years ago... in fact I set it up shortly after geli went into
FreeBSD. I suspect that defaults changed since then and, when I got my new
system, instead of using DD to image the file system, I created a new
encrypted system with current defaults and copied the data from my backup
drive.

I am embarrassed to admit that I didn't even think about this rather
drastic change in the file system. Thanks so much for the help! Sorry to
have wasted whatever time you spent thinking about my concern.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: How do I know if my 13-stable has security patches?

[Kevin Oberman]

On Thu, Feb 25, 2021 at 6:10 AM Ed Maste  wrote:

> On Thu, 25 Feb 2021 at 02:42, Kevin Oberman  wrote:
> >
> > Thanks, Ed, but where do I find this? uname -a" gives me
> stable/13-007101f87. For a while I was seeing a hyphenated number prefixed
> with a 'c' and I had assumed that that number was the sequence.
>
> It is (was) - we changed from 'c' to avoid having it look like a hex value.
>
> To generate (this part of) uname the build script runs:
> if [ "$($git_cmd rev-parse --is-shallow-repository)" = false ] ;
> then
> git_cnt=$($git_cmd rev-list --first-parent --count
> HEAD 2>/dev/null)
> if [ -n "$git_cnt" ] ; then
> git="n${git_cnt}-${git}"
> fi
> fi
>
> Would you try running, at the top of your stable/13 src tree:
> git rev-parse --is-shallow-repository
> git rev-list --first-parent --count HEAD
>

I do run a shallow clone, as I suspect most non-developers will.
# git rev-parse --is-shallow-repository
true
# git rev-list --first-parent --count HEAD
133

As for an easy check for the presence of a patch by hash, I like the "git
log --pretty=oneline" | grep  

This assumes that the sources have NOT been updated since the system was
updated. If they have, you can do a "egrep -n ^" on both the partial
hash in "uname -a" and in the security announcement and see which is older
by line number.

My thanks to Jeremy Chadwick for this approach.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: How do I know if my 13-stable has security patches?

[Kevin Oberman]

Thanks, Ed, but where do I find this? uname -a" gives me
stable/13-007101f87. For a while I was seeing a hyphenated number prefixed
with a 'c' and I had assumed that that number was the sequence. The full
hash from the logs just is a long hex number. As usual with git stuff, I'm
still very confused. After decades with a common paradigm with RCS CVS and
SVN, git is fundamentally very different and old terminology does not
really align as git is designed from a  very different perspective.

I have read the little mini-guide Warner wrote as well as a couple of web
tutorial, but the web tutorials are really about running your own repo on
github or gitlab, not using a repo as a source for distributions. I'm still
a long way from having a real clue.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


On Wed, Feb 24, 2021 at 12:06 PM Ed Maste  wrote:

> On Wed, 24 Feb 2021 at 12:35, Kevin Oberman  wrote:
> >
> > In the svn days, I could just look at my svn revision to check on
> whether a
> > security patch was required. Now I have a git hash. I have no idea how to
> > tell if my system running 13-STABLE of a few days ago has the patch.
>
> Thanks for posting this question. I see some useful information in
> other replies to this thread and we'll want to make sure that makes
> its way to appropriate documentation.
>
> For future advisories we should also report the commit count
> associated with the fix; this is a monotonically-increasing number and
> is reported in the uname.
>
> If you build stable/13 right now you would get
> "stable/13-n244668-4664afc05402", and the fix in
> 894360bacd42f021551f76518edd445f6d299f2e corresponds to n244572.
> 244668 being larger than 244572 indicates that the fix is included.
>
> These counts are not unique across different branches; you can only
> compare counts for the same branch.
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Drastic slowdown for geli attach

[Kevin Oberman]

Sometime around the first week of this month (February) the time to do a
geli attach on my 13.0-ALPHA3 amd64 system sharply increased. It started
taking about 10 seconds. Prior to this, it took about 3-4 seconds. I have
not seen any issues with the disc after it attaches, I am simply concerned
that the longer time may be indicative of a deeper issue.

The system is a ThinkPad L15 with a CometLake i5-10210U and a Seagate
ST2000LM007-1R8174 2T HDD.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: How do I know if my 13-stable has security patches?

[Kevin Oberman]

Thanks, Olivier, for the quick response. Now I don't have to do a system
build!

Neither command is what I'd call 'intuitive', so it would have taken me a
long time to find either of them. I cut and pasted the 'git branch' command
and it took me a moment to realize what that meant. Never ran "grep -l" on
a pipe, I guess.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


On Wed, Feb 24, 2021 at 10:06 AM Olivier Certner 
wrote:

> Hi,
>
> In your base git repository, type:
> git rev-list  | grep -lF 
>
> This outputs something ("(standard input)") iff you have it in.
>
> In order to limit the search time in case of a false result, you'd better
> pass
> the --since= to git rev-list.
>
> There is an alternative if you have a branch pointing to your uname hash:
> git branch --contains  | grep -lF 
>
> Regards.
>
> --
> Olivier Certner
>
>
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

How do I know if my 13-stable has security patches?

[Kevin Oberman]

In the svn days, I could just look at my svn revision to check on whether a
security patch was required. Now I have a git hash. I have no idea how to
tell if my system running 13-STABLE of a few days ago has the patch.

Branch/path  Revision
- -
stable/13/   894360bacd42f021551f76518edd445f6d299f2e
releng/13.0/ 9f00cb5fa8a438e7b9efb2158f2e2edc730badd1
stable/12/r369312
releng/12.2/  r369353

Is there a git command that can confirm whether a given hash is covered in
my system?
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD 13.0-BETA2 and slow IO

[Kevin Oberman]

On Tue, Feb 16, 2021 at 3:06 AM Konstantin Belousov 
wrote:

> On Tue, Feb 16, 2021 at 12:54:55PM +0200, Christos Chatzaras wrote:
> >
> > > On 16 Feb 2021, at 12:20, Christos Chatzaras 
> wrote:
> > >
> > > I build a test system with 13.0-BETA2 and it's very slow with at least
> IO.
> > >
> > > Doing "portsnap auto" takes much more time than 12.2.
> > >
> > > Also when I do "rm -fr /usr/ports" with 12.2 takes 5 seconds and the
> same command with 13.0-BETA2 takes 100 seconds.
> > >
> > > The disks are similar 4TB HDD drives on both systems.
> > >
> > > Is this related to debug enabled in 13.0-BETA2?
> >
> > I install 12.2 in the same system and "rm -fr /usr/ports" was fast. So
> it's not related to hardware.
> >
> > If I upgrade it to 13.0-BETA2 the same command is slow again.
>
> Are you using UFS+SU or SU+J?  If yes, this is known and fix is planned
> for BETA3 or BETA4.
>
A note to this thread when it is committed to rewleng or stable would be
greatly appreciated.  The time to download and unpack a large port distfile
(e.g. firefox) is painful. I'm hoping this is causing it as I just had the
disk on my new laptop replaced 6 months ago and I was afraid that it was
failing again.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Upgrading, 11.4 -> 12.1

[Kevin Oberman]

On Mon, Aug 31, 2020 at 1:05 PM Kurt Jaeger  wrote:

> Hi!
>
> > > I'm guessing: Do you have the dbus and hald daemon running ?
> > >
> > > hald_enable="YES"
> > > dbus_enable="YES"
> > >
> > > in /etc/rc.conf ?
> > >
> > Yes, I do.  Should I disable them, then? -- George
>
> No, they are needed.
>
> You mentioned that you build the x11 stuff on 11.3. I do not know
> if this works, I have my doubts.
>
> --
> p...@opsec.eu+49 171 3101372Now what ?
>
This question would be both more appropriate and more likely to get a
knowledgeable response if submitted to x11@. X is not part of the base
system although a base system upgrade did trigger the problem.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: drm-kmod i915kms.ko no result from pkg

[Kevin Oberman]

Ack! This is make(1), not sh(1).  "PORTS_MODULES = /path/to/port/directory"
for the first and '+=' for subsequent ports.

Sorry for the braino.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


On Fri, Aug 7, 2020 at 4:37 PM Kevin Oberman  wrote:

> On Fri, Aug 7, 2020 at 4:02 PM Pete Wright  wrote:
>
>>
>>
>> On 8/7/20 7:39 AM, Dmitrii Postolov wrote:
>> > Hi to all! Sorry for my bad English...
>> >
>> > dmitrii@nuc7:~ % uname -a
>> > FreeBSD nuc7 12.1-STABLE FreeBSD 12.1-STABLE r363918 GENERIC  amd64
>> >
>> > Intel NUC7PJYH2 Intel HD Graphics.
>> >
>> > drm-kmod i915kms.ko no result if install from pkg. User in video group.
>> > in /etc/rc.conf: kld_list="/boot/modules/i915kms.ko"
>> >
>> > The workaround: build drm-kmod from ports after that all OK.
>> >
>> > This is regression for 12.1-STABLE, for 12.1-RELEASE all OK.
>> I believe that is somewhat expected because there may be changes to the
>> KPI in STABLE that have not been merged to a RELEASE branch yet.  So
>> since the packages are built against RELEASE branches you will run into
>> issues where you need to build the DRM drivers locally for systems
>> running both STABLE and CURRENT.
>>
>> Cheers,
>> -pete
>>
>> --
>> Pete Wright
>> p...@nomadlogic.org
>> @nomadlogicLA
>>
> More simply, if you run *-STABLE or CURRENT, you really need to rebuild
> kmod ports every time you rebuild the kernel. If you are using snapshots
> and not rebuilding, you need to at least keep the kernel sources
> (/usr/src/sys) on a system and then rebuild any kmod ports when you update
> the system. Also, lsof requires current kernel sources, so I suggest
> "PORTS_MODULES?=/apth/to/port directory" for any of them in your
> /etc/src.conf.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: drm-kmod i915kms.ko no result from pkg

[Kevin Oberman]

On Fri, Aug 7, 2020 at 4:02 PM Pete Wright  wrote:

>
>
> On 8/7/20 7:39 AM, Dmitrii Postolov wrote:
> > Hi to all! Sorry for my bad English...
> >
> > dmitrii@nuc7:~ % uname -a
> > FreeBSD nuc7 12.1-STABLE FreeBSD 12.1-STABLE r363918 GENERIC  amd64
> >
> > Intel NUC7PJYH2 Intel HD Graphics.
> >
> > drm-kmod i915kms.ko no result if install from pkg. User in video group.
> > in /etc/rc.conf: kld_list="/boot/modules/i915kms.ko"
> >
> > The workaround: build drm-kmod from ports after that all OK.
> >
> > This is regression for 12.1-STABLE, for 12.1-RELEASE all OK.
> I believe that is somewhat expected because there may be changes to the
> KPI in STABLE that have not been merged to a RELEASE branch yet.  So
> since the packages are built against RELEASE branches you will run into
> issues where you need to build the DRM drivers locally for systems
> running both STABLE and CURRENT.
>
> Cheers,
> -pete
>
> --
> Pete Wright
> p...@nomadlogic.org
> @nomadlogicLA
>
More simply, if you run *-STABLE or CURRENT, you really need to rebuild
kmod ports every time you rebuild the kernel. If you are using snapshots
and not rebuilding, you need to at least keep the kernel sources
(/usr/src/sys) on a system and then rebuild any kmod ports when you update
the system. Also, lsof requires current kernel sources, so I suggest
"PORTS_MODULES?=/apth/to/port directory" for any of them in your
/etc/src.conf.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: swap space issues

[Kevin Oberman]

On Thu, Jun 25, 2020 at 4:42 AM Donald Wilde  wrote:

> On 6/24/20, Kevin Oberman  wrote:
> > On Wed, Jun 24, 2020 at 10:30 PM Greg 'groggy' Lehey 
> > wrote:
> >
> >> On Wednesday, 24 June 2020 at 20:34:24 -0700, Donald Wilde wrote:
> >> > On 6/24/20, Greg 'groggy' Lehey  wrote:
> >> >> On Wednesday, 24 June 2020 at 18:51:04 -0700, Donald Wilde wrote:
> >> >>> On 6/24/20, Greg 'groggy' Lehey  wrote:
> >> >>>> On Wednesday, 24 June 2020 at  9:36:23 -0700, Donald Wilde wrote:
> >> >>>>> All,
> >> >>>>>
> >> >>>>> I recently upgraded my 12-STABLE system to the latest, and now my
> >> >>>>> swap subsystems aren't working. I deliberately set up a 40GB
> >> >>>>> partition for swap, and when I do 'top -t' I am only seeing 7906M
> >> >>>>> total.
> >> >>>>
> >> >>>> That looks suspiciously like the difference from 32 GB.  Could it
> be
> >> >>>> numeric overflow?  And if so, where?  What does pstat -s say?
> >> >>>
> >> >>> Well, hi Greg! LTNT2!
> >> >>
> >> >> Indeed.
> >> >>
> >> >>> pstat -shm:
> >> >>>
> >> >>> /dev/ada0s1b  65536 (1M blocks), Used: 1.5G, Avail: 63G, Capacity:
> 2%
> >> >>
> >> >> Now that's really puzzling.  Why does it say 64 G when you said 40 G,
> >> >> and the error from top tends to confirm it?  How big is the partition
> >> >> (gpart output)?
> >> >
> >> > Attached 'gpart list' output
> >>
> >> FWIW, gpart show would have done the job.  But what I see there is Yet
> >> Another swap partition size, 66 GB.   So so far we have various parts
> >> reporting 8 GB, 40 GB, 64 GB and 66 GB.
> >>
> >> > Reduced kern.maxswzone to 999. Is it decimal or unlabeled hex?
> >>
> >> It'll be decimal, but it refers to the number of swblk structures
> >> assigned in memory, and after reading the code I'm still not 100% in
> >> the clear how this relates to the size of swap, if at all.
> >>
> >> > 'top' now shows 4597M total swap.
> >>
> >> ... and 4.6 GB.  5 different sizes.
> >>
> >> You really shouldn't be relying on top for swap info.  It's a third
> >> party program that demonstrably shows incorrect results (though I
>
> I was continuing to reference it because its 'incorrect results' might
> flag where we need to see things working. When 'top' shows the right
> results, we've fixed the right thing.
>
> >> believe that the maintainer would be very interested to know why and
> >> to fix it).  But pstat -s (without any further options) should show
> >> what the kernel thinks.
>
> Here's what I see immediately following shutdown -r and boot:
>
> Device  1K-blocks UsedAvail Capacity
> /dev/ada0s1b 671088640 67108864 0%
>
> >>
> >> >>> What else can I share to help diagnose this?
> >> >>
> >> >> Background, maybe?  You say that you upgraded your system.  Did you
> >> >> change the swap size when you did?  What were swap and RAM sizes
> >> >> before and after?
> >> >
> >> > Meant that I upgraded from 12.1-RELEASE to 12-STABLE. When I
> >> > configured the -RELEASE install, I manually messed with the MBR disk
> >> > partitions. This is nominally a half-TB HDD which showed up as a total
> >> > of 446 G available (IIRC, gpart should show it's actual size). I did
> >> > auto partitioning, looked at the sizes, and manually set my partitions
> >> > to give me 40G of swap instead of the auto-generated size of 4G.
> >>
> >> That's really puzzling.  It seems that it gave you much more than you
> >> asked for.
> >>
> >> Try this in single user mode: modify the size of the swap partition to
> >> 30 GB.  I haven't used MBR partitions for years now, but I believe
> >> that 'bsdlabel -e' will do the trick.  Just shorten the length of the
> >> b partition.  You may need to 'mount -u /'.  If you do it right
> >> (check!), this won't harm any of the other partitions: it'll just
> >> leave 26 GB free between the swap partition and the next partition.
>
> Thanks again, Greg!
>
> >>
> > gpart(8) works just fine on MBR drives and partitions/slices and has a
> much
> > 

Re: swap space issues

[Kevin Oberman]

On Wed, Jun 24, 2020 at 10:30 PM Greg 'groggy' Lehey 
wrote:

> On Wednesday, 24 June 2020 at 20:34:24 -0700, Donald Wilde wrote:
> > On 6/24/20, Greg 'groggy' Lehey  wrote:
> >> On Wednesday, 24 June 2020 at 18:51:04 -0700, Donald Wilde wrote:
> >>> On 6/24/20, Greg 'groggy' Lehey  wrote:
> >>>> On Wednesday, 24 June 2020 at  9:36:23 -0700, Donald Wilde wrote:
> >>>>> All,
> >>>>>
> >>>>> I recently upgraded my 12-STABLE system to the latest, and now my
> >>>>> swap subsystems aren't working. I deliberately set up a 40GB
> >>>>> partition for swap, and when I do 'top -t' I am only seeing 7906M
> >>>>> total.
> >>>>
> >>>> That looks suspiciously like the difference from 32 GB.  Could it be
> >>>> numeric overflow?  And if so, where?  What does pstat -s say?
> >>>
> >>> Well, hi Greg! LTNT2!
> >>
> >> Indeed.
> >>
> >>> pstat -shm:
> >>>
> >>> /dev/ada0s1b  65536 (1M blocks), Used: 1.5G, Avail: 63G, Capacity: 2%
> >>
> >> Now that's really puzzling.  Why does it say 64 G when you said 40 G,
> >> and the error from top tends to confirm it?  How big is the partition
> >> (gpart output)?
> >
> > Attached 'gpart list' output
>
> FWIW, gpart show would have done the job.  But what I see there is Yet
> Another swap partition size, 66 GB.   So so far we have various parts
> reporting 8 GB, 40 GB, 64 GB and 66 GB.
>
> > Reduced kern.maxswzone to 999. Is it decimal or unlabeled hex?
>
> It'll be decimal, but it refers to the number of swblk structures
> assigned in memory, and after reading the code I'm still not 100% in
> the clear how this relates to the size of swap, if at all.
>
> > 'top' now shows 4597M total swap.
>
> ... and 4.6 GB.  5 different sizes.
>
> You really shouldn't be relying on top for swap info.  It's a third
> party program that demonstrably shows incorrect results (though I
> believe that the maintainer would be very interested to know why and
> to fix it).  But pstat -s (without any further options) should show
> what the kernel thinks.
>
> >>> What else can I share to help diagnose this?
> >>
> >> Background, maybe?  You say that you upgraded your system.  Did you
> >> change the swap size when you did?  What were swap and RAM sizes
> >> before and after?
> >
> > Meant that I upgraded from 12.1-RELEASE to 12-STABLE. When I
> > configured the -RELEASE install, I manually messed with the MBR disk
> > partitions. This is nominally a half-TB HDD which showed up as a total
> > of 446 G available (IIRC, gpart should show it's actual size). I did
> > auto partitioning, looked at the sizes, and manually set my partitions
> > to give me 40G of swap instead of the auto-generated size of 4G.
>
> That's really puzzling.  It seems that it gave you much more than you
> asked for.
>
> Try this in single user mode: modify the size of the swap partition to
> 30 GB.  I haven't used MBR partitions for years now, but I believe
> that 'bsdlabel -e' will do the trick.  Just shorten the length of the
> b partition.  You may need to 'mount -u /'.  If you do it right
> (check!), this won't harm any of the other partitions: it'll just
> leave 26 GB free between the swap partition and the next partition.
>
gpart(8) works just fine on MBR drives and partitions/slices and has a much
friendlier user interface. "gpart resize"  is the command you want.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: circular dependency on print/tex-dvipsk

[Kevin Oberman]

On Fri, Jun 5, 2020 at 6:38 PM Donald Wilde  wrote:

> I've been doing some more work to get to the bottom of why my synth
> upgrade-system stalled.
>
> Here's the pertinent line, though the whole operation's result is attached.
>
> print/tex-dvipsk scan aborted because a circular dependency on
> print/tex-dvipsk was detected.
>
> If I understand this it means that two different programs require two
> _different_ versions of the tex-dvipsk program to be installed.
> Correct? At this point, it seems to be beyond a 'how did I get here'
> situation, it's a 'discover which programs cause it' situation.
>
> Iterating through the list of installed packages to see where two
> different packages depend on different versions of tex-dvipsk. That is
> the only possible reason for such a dependency, yes?
>
>
> --
> Don Wilde


Not quite. A circular dependency means that Port-A depends on Port-B and
Port-B depends on Port-A, though it is normally not so obvious as there are
usually intervening ports in the dependency path.

It seems that this should show up during a poudriere builds, too, so it
would be caught quickly. Not sure why synth (which I have not used in
years) would have an issue when poudriere (which I have never used) does
not.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: New Xorg - different key-codes

[Kevin Oberman]

On Wed, Mar 11, 2020 at 1:51 PM Greg Rivers 
wrote:

> On Wednesday, 11 March 2020 13:53:45 CDT Peter Jeremy wrote:
> > On 2020-Mar-11 10:29:08 +0100, Niclas Zeising 
> wrote:
> > >This has to do with switching to using evdev to handle input devices on
> > >FreeBSD 12 and CURRENT.  There's been several reports, and suggested
> > >solutions to this, as well as an UPDATING entry detailing the change.
> >
> > The UPDATING entry says that it's switched from devd to udev.  There's no
> > mention of evdev or that the keycodes have been roto-tilled.  It's
> basically
> > a vanilla "things have been changed, see the documentation" entry.  Given
> > that entry, it's hardly surprising that people are confused.
> >
> Indeed, the change has been a bit inconvenient and time consuming to deal
> with.
>
> But I don't think we should let this overshadow the dedication and very
> hard work that Niclas and the graphics team have done and continue to do to
> keep FreeBSD relevant on the desktop. I for one am very grateful for that.
>
> --
> Greg
>

And the people involved have been very active in helping people resolve the
problems. In particular, Michael Gmelin had been very helpful in providing
a workaround for the failure of the brightness control buttons on my rather
ancient T520. He has also provided a solution for the failure of the volume
control buttons that I've had since the last update to MATE. I have yet to
try it as something else (no idea what) had magically fixed this after a
couple of months of them not working. I can't figure out what "fixed" this,
but it just started working a couple of weeks ago. Until/unless it fails,
I'm not touching things.

Also, my apologies to Michael as I have not responded to him with a status
update for WAY too long.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: jedec_dimm fails to boot

[Kevin Oberman]

On Wed, Mar 4, 2020 at 9:14 AM Peter  wrote:

>
> I met an Issue:
>
> When I kldload jedec_dimm durig runtime, it works just as expected,
> and the DIMM data appears in sysctl.
>
> But when I do
>  * load the jedec_dimm at the loader prompt, or
>  * add it to loader.conf, or
>  * compile it into a custom kernel,
> it does not boot anymore.
>
> My custom kernel does just hang somewhere while switching the screen,
> i.e. no output. The GENERIC does immediate-reboot during the device
> probe phase. So both are not suitable for gathering additional info
> in an easy way. (And since my DIMM appear to have neither thermal nor
> serial, there is not much to gain for me here, so I will not pursue
> this further, at least not before switching to R.12.)
> But I fear there are some general problems with sorting out of the
> modules during system bringup - see also my other message titled
> "panic: too many modules".
>
> Some data for those interested:
>
> FreeBSD 11.3-RELEASE-p6
> CPU: Intel(R) Core(TM) i5-3570T CPU (IvyBridge)
> Board: https://www.asus.com/Motherboards/P8B75V/specifications/
> Config:
> hint.jedec_dimm.0.at="smbus12"
> hint.jedec_dimm.0.addr="0xa0"
> hint.jedec_dimm.1.at="smbus12"
> hint.jedec_dimm.1.addr="0xa2"
> hint.jedec_dimm.2.at="smbus12"
> hint.jedec_dimm.2.addr="0xa4"
> hint.jedec_dimm.3.at="smbus12"
> hint.jedec_dimm.3.addr="0xa6"
>
> ichsmb0:  port 0xf040-0xf05f mem
> 0xf7d1500
> 0-0xf7d150ff irq 18 at device 31.3 on pci0
> smbus12:  on ichsmb0
> smb12:  on smbus12
>
> With GENERIC it becomes smbus0 (because drm2 is not loaded) and I need
> to load "smbus" and "ichsmb" frontup.
>
> Cheerio,
> PMc
>

Looks like you just need the module loaded a bit later.

Does adding kld_list="jedec_dimm.kld" to /etc/rc.conf work? If you already
have kld_list, append "jedec_dimm".
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: input devices after xorg update

[Kevin Oberman]

On Sat, Feb 22, 2020 at 12:06 PM Nuno Teixeira  wrote:

> Hi,
>
> More on udev libinput:
>
> New Xorg switch from devd to udev
> <
> https://forums.freebsd.org/threads/new-xorg-switch-from-devd-to-udev.74144/
> >
>
> Nuno Teixeira
>
>  escreveu no dia sábado, 22/02/2020 à(s) 16:54:
>
> > Hi,
> >
> > after taking quite a while to get a working x11 back, here's what
> > I learned: if you build everything from ports, it is important to
> > revisit the configured options on your x11 related ports. You need to
> > enable the libinput driver and on FreeBSD 12 or newer switch xorg-server
> > to using udev. While this is now default, your stored build options
> > might be different.
> >
> > For everyone using non-default keyboard layouts, configured as in
> > section 5.4.7.1 of the FreeBSD handbook: you now need to use the
> > "libinput" driver instead of "keyboard". Otherwise the keyboard
> > module gets loaded in addition to the libinput module, resulting in
> > both talking to the keyboard and rendering it unusable.
> >
> > Wolfgang


I have everything working again. I had to install the small patch in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244306
and follow the instructions in the pkg-message. I did NOT switch to UDEV. I
sill use the default of DEVD. I do have libinput and xf86-input-evdev
installed.

It appears that the FIXDRM patch is only required on certain hardware... in
my case a Sandy Bridge GPU.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Light GeoIP support dropped?

[Kevin Oberman]

On Mon, Jan 6, 2020 at 1:17 PM Alexander Koeppe  wrote:

> Hi,
>
> since I've upgraded to FreeBSD 12, I don't find a package providing the
> lightweight geoip database API incl. GeoIP.h and libGeoIP.so.
>
> I only find `geoipupdate` which is the non-free variant of the API.
>
> Has the package been renamed?
>
> Thanks
>
>- Alex


GeoIP and the GeoIP 1 database were discontinued early last year. They were
replaced by net/libmaxminddb and GeoIP 2 database. I have no idea if any
form of free data is available.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Memory management changes after kernel update on 6-Aug

[Kevin Oberman]

On Fri, Aug 9, 2019 at 5:34 PM Kevin Oberman  wrote:

>
>
> On Fri, Aug 9, 2019 at 2:16 PM Mark Johnston  wrote:
>
>> On Fri, Aug 09, 2019 at 01:05:50PM -0700, Kevin Oberman wrote:
>> > On Fri, Aug 9, 2019 at 11:35 AM Mark Johnston 
>> wrote:
>> >
>> > > On Fri, Aug 09, 2019 at 11:09:24AM -0700, Kevin Oberman wrote:
>> > > > Since I updated my 12.0-STABLE system on 6-Aug I have been seeing
>> issues
>> > > > resuming my Win7 VM on VirtualBox. My prior kernel was built on
>> 24-Jul.
>> > > If
>> > > > there is not sufficient memory available to reload the system (4
>> Meg.),
>> > > the
>> > >
>> > > Where does this number come from?  What memory usage stats do you see
>> in
>> > > top(1) when the error occurs?
>> > >
>> >
>> > I am monitoring memory usage with gkrellm. It appears to define "Free"
>> as
>> > the sum of "Inactive" and "Free". If you are referring to size of the
>> VM,
>> > was supposed to be the memory specified when I created the VM, but my
>> > fingers got ahead of my brain and it should have been 4G, not 4M. Hey!
>> > What's a few orders of magnitude?
>> >
>> > Oddly, when I watch memory space closely I note that, as the VM loads, I
>> > started seeing swap utilization increase as free space was exhausted at
>> > about 80% loaded. Loading continued to 98%. at that point loading
>> stopped
>> > and swap use continued to grow for a bit. Then free space started to
>> > increase from about 300M to about 700M before the error window popped
>> up.
>> >
>> >
>> > > > resume fails with a message that memory was exhausted. Usually I
>> can try
>> > > > resuming again and it will work. Sometimes I get the error two or
>> three
>> > > > times before the system resumes.
>> > >
>> > > What exactly is the error message?
>> > >
>> > Failed to open a session for the virtual machine Win7.
>> >
>> > Failed to load unit 'pgm' (VERR_EM_NO_MEMORY).
>> >
>> > Result Code: NS_ERROR_FAILURE (0x80004005)
>> > Component: ConsoleWrap
>> > Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
>> >
>> >
>> > >
>> > > > Since I have not touched VirtualBox other than to rebuild the kmod
>> after
>> > > > the kernel build, it looks like something in the OS triggered this.
>> Since
>> > > > the system frees up some memory each time so that the VM eventually
>> > > > resumes, it looks like the memory request is made to the OS, but VB
>> is
>> > > not
>> > > > waiting or not enough memory is freed to allow the VB to complete
>> the
>> > > > resume.
>> > > >
>> > > > Any clue what might have changed over those 13 days? I am running
>> GENERIC
>> > > > except that I run the 4BSD scheduler.
>> > >
>> > > Possible culprits are r350374 and r350375, but I can't really see how.
>> > >
>> >
>> > This started after the 6-Aug build (r350664). My prior build was
>> r350292,
>> > so just before these two commits.
>> >
>> > Can I try just reverting these two? Once I do, it will need to run for a
>> > while or do something to tie up a lot of memory before the error will
>> > recur. In normal use it is a matter of firefox increasing resident
>> memory
>> > until there is not enough free memory to load the VM without swapping.
>> > (These days I often see the sum of all firefox process resident memory
>> > exceeding 3G after it's been up for a day or two. Still, not worse than
>> > chromium.)
>>
>> Those commits can simply be reverted, but I am skeptical that they will
>> help.  You should also verify that these same conditions don't lead to
>> errors on your prior build, if you haven't already.
>>
>
> OK. Running identical kernel except for 350374-5.
>
> Yes, I am sure that it was not happening with the r350292 kernel. I hit
> this quite consistently when firefox has been running for a while.
>
> Firefox has rss of just under 3G on startup and will slowly grow until I
> don't have the resources to run the Win7 VM without the error. Right now
> the VM completes loading with no swapping and about 800M of memory free
> after it is running. I'll let you know when it gets big enoug

Re: Memory management changes after kernel update on 6-Aug

[Kevin Oberman]

On Fri, Aug 9, 2019 at 2:16 PM Mark Johnston  wrote:

> On Fri, Aug 09, 2019 at 01:05:50PM -0700, Kevin Oberman wrote:
> > On Fri, Aug 9, 2019 at 11:35 AM Mark Johnston  wrote:
> >
> > > On Fri, Aug 09, 2019 at 11:09:24AM -0700, Kevin Oberman wrote:
> > > > Since I updated my 12.0-STABLE system on 6-Aug I have been seeing
> issues
> > > > resuming my Win7 VM on VirtualBox. My prior kernel was built on
> 24-Jul.
> > > If
> > > > there is not sufficient memory available to reload the system (4
> Meg.),
> > > the
> > >
> > > Where does this number come from?  What memory usage stats do you see
> in
> > > top(1) when the error occurs?
> > >
> >
> > I am monitoring memory usage with gkrellm. It appears to define "Free" as
> > the sum of "Inactive" and "Free". If you are referring to size of the VM,
> > was supposed to be the memory specified when I created the VM, but my
> > fingers got ahead of my brain and it should have been 4G, not 4M. Hey!
> > What's a few orders of magnitude?
> >
> > Oddly, when I watch memory space closely I note that, as the VM loads, I
> > started seeing swap utilization increase as free space was exhausted at
> > about 80% loaded. Loading continued to 98%. at that point loading stopped
> > and swap use continued to grow for a bit. Then free space started to
> > increase from about 300M to about 700M before the error window popped up.
> >
> >
> > > > resume fails with a message that memory was exhausted. Usually I can
> try
> > > > resuming again and it will work. Sometimes I get the error two or
> three
> > > > times before the system resumes.
> > >
> > > What exactly is the error message?
> > >
> > Failed to open a session for the virtual machine Win7.
> >
> > Failed to load unit 'pgm' (VERR_EM_NO_MEMORY).
> >
> > Result Code: NS_ERROR_FAILURE (0x80004005)
> > Component: ConsoleWrap
> > Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
> >
> >
> > >
> > > > Since I have not touched VirtualBox other than to rebuild the kmod
> after
> > > > the kernel build, it looks like something in the OS triggered this.
> Since
> > > > the system frees up some memory each time so that the VM eventually
> > > > resumes, it looks like the memory request is made to the OS, but VB
> is
> > > not
> > > > waiting or not enough memory is freed to allow the VB to complete the
> > > > resume.
> > > >
> > > > Any clue what might have changed over those 13 days? I am running
> GENERIC
> > > > except that I run the 4BSD scheduler.
> > >
> > > Possible culprits are r350374 and r350375, but I can't really see how.
> > >
> >
> > This started after the 6-Aug build (r350664). My prior build was r350292,
> > so just before these two commits.
> >
> > Can I try just reverting these two? Once I do, it will need to run for a
> > while or do something to tie up a lot of memory before the error will
> > recur. In normal use it is a matter of firefox increasing resident memory
> > until there is not enough free memory to load the VM without swapping.
> > (These days I often see the sum of all firefox process resident memory
> > exceeding 3G after it's been up for a day or two. Still, not worse than
> > chromium.)
>
> Those commits can simply be reverted, but I am skeptical that they will
> help.  You should also verify that these same conditions don't lead to
> errors on your prior build, if you haven't already.
>

OK. Running identical kernel except for 350374-5.

Yes, I am sure that it was not happening with the r350292 kernel. I hit
this quite consistently when firefox has been running for a while.

Firefox has rss of just under 3G on startup and will slowly grow until I
don't have the resources to run the Win7 VM without the error. Right now
the VM completes loading with no swapping and about 800M of memory free
after it is running. I'll let you know when it gets big enough to cause a
problem and whether it fails. Probably won't happen until tomorrow.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Memory management changes after kernel update on 6-Aug

[Kevin Oberman]

On Fri, Aug 9, 2019 at 11:35 AM Mark Johnston  wrote:

> On Fri, Aug 09, 2019 at 11:09:24AM -0700, Kevin Oberman wrote:
> > Since I updated my 12.0-STABLE system on 6-Aug I have been seeing issues
> > resuming my Win7 VM on VirtualBox. My prior kernel was built on 24-Jul.
> If
> > there is not sufficient memory available to reload the system (4 Meg.),
> the
>
> Where does this number come from?  What memory usage stats do you see in
> top(1) when the error occurs?
>

I am monitoring memory usage with gkrellm. It appears to define "Free" as
the sum of "Inactive" and "Free". If you are referring to size of the VM,
was supposed to be the memory specified when I created the VM, but my
fingers got ahead of my brain and it should have been 4G, not 4M. Hey!
What's a few orders of magnitude?

Oddly, when I watch memory space closely I note that, as the VM loads, I
started seeing swap utilization increase as free space was exhausted at
about 80% loaded. Loading continued to 98%. at that point loading stopped
and swap use continued to grow for a bit. Then free space started to
increase from about 300M to about 700M before the error window popped up.


> > resume fails with a message that memory was exhausted. Usually I can try
> > resuming again and it will work. Sometimes I get the error two or three
> > times before the system resumes.
>
> What exactly is the error message?
>
Failed to open a session for the virtual machine Win7.

Failed to load unit 'pgm' (VERR_EM_NO_MEMORY).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}


>
> > Since I have not touched VirtualBox other than to rebuild the kmod after
> > the kernel build, it looks like something in the OS triggered this. Since
> > the system frees up some memory each time so that the VM eventually
> > resumes, it looks like the memory request is made to the OS, but VB is
> not
> > waiting or not enough memory is freed to allow the VB to complete the
> > resume.
> >
> > Any clue what might have changed over those 13 days? I am running GENERIC
> > except that I run the 4BSD scheduler.
>
> Possible culprits are r350374 and r350375, but I can't really see how.
>

This started after the 6-Aug build (r350664). My prior build was r350292,
so just before these two commits.

Can I try just reverting these two? Once I do, it will need to run for a
while or do something to tie up a lot of memory before the error will
recur. In normal use it is a matter of firefox increasing resident memory
until there is not enough free memory to load the VM without swapping.
(These days I often see the sum of all firefox process resident memory
exceeding 3G after it's been up for a day or two. Still, not worse than
chromium.)

Thanks, Mark, for the quick response.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Memory management changes after kernel update on 6-Aug

[Kevin Oberman]

Since I updated my 12.0-STABLE system on 6-Aug I have been seeing issues
resuming my Win7 VM on VirtualBox. My prior kernel was built on 24-Jul. If
there is not sufficient memory available to reload the system (4 Meg.), the
resume fails with a message that memory was exhausted. Usually I can try
resuming again and it will work. Sometimes I get the error two or three
times before the system resumes.

Since I have not touched VirtualBox other than to rebuild the kmod after
the kernel build, it looks like something in the OS triggered this. Since
the system frees up some memory each time so that the VM eventually
resumes, it looks like the memory request is made to the OS, but VB is not
waiting or not enough memory is freed to allow the VB to complete the
resume.

Any clue what might have changed over those 13 days? I am running GENERIC
except that I run the 4BSD scheduler.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problem with STABLE-12 amd 64

[Kevin Oberman]

On Mon, Jul 15, 2019 at 12:50 PM Jonathan Chen  wrote:

> On Mon, 15 Jul 2019 at 22:28, Filippo Moretti via freebsd-stable
>  wrote:
> >
> >  I did build world but it did not solve the problem
>
> You need to rebuild the port, graphics/drm-kmod, as this port contains
> kernel modules. Whenever you upgrade the base system, it is always a
> good idea to rebuild/reinstall ports that contain kernel modules, as
> they get depend quite critically on being in sync.
>
> Cheers.
> --
> Jonathan Chen 
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>

If you can't resolve the issue, please report how you load the kernel
module and the exact version of the drm-kmod you have installed.you can get
it with "pkg info drm-\*".  You should get two lines, one for drm-kmod and
another for module installed. Also, I don't recall whether you reported the
exact GPU you have on your system. Won't help me, but others, more familiar
with AMD may find it useful. Finally, "kldstat -v | grep -A 1 -E "drm|kms""
will provide the exact ID and filename of the loaded kernel modules.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problem with STABLE-12 amd 64

[Kevin Oberman]

On Sun, Jul 14, 2019 at 2:42 AM Filippo Moretti via freebsd-stable <
freebsd-stable@freebsd.org> wrote:

> I get the following error:KLD radeonkms.ko: depends on kernel -not
> available or version
> mismatch linker_load_file:/boot/modules/radeonkms.ko-unsupported file
> typeany suggestion on how to fix it appreciatedsincerelyFilipo
>
Looks like your kernel module, radeonkms.ko, is not in sync with your
kernel.

Have you upgraded you kernel? It is always a good idea to rebuild kernel
modules whenever you build a kernel. This is easily accomplished by adding
"PORTS_MODULES=graphics/drm-kmod" to /etc/src.conf.

For an immediate fix, just re-install the port from source.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: ZFS...

[Kevin Oberman]

On Sat, May 4, 2019 at 12:38 PM Chris  wrote:

> Sorry t clarify, Michelle I do believe your tail of events, just I
> meant that it reads like a tale as its so unusual.
>
As the late Sir Terry Pratchett wrote, "Scientists have calculated that the
chances of something so patently absurd actually existing are millions to
one. But magicians have calculated that million-to-one chances crop up nine
times out of ten.”
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: ltmain.sh not found

[Kevin Oberman]

On Wed, Apr 24, 2019 at 9:05 AM Christoph Moench-Tegeder 
wrote:

> ## Willem Offermans (wil...@offermans.rompen.nl):
>
> > Unfortunately it is probably not gawk in my case, which causes trouble.
> > However, your response indicates that the problem will be solved after I
> > have updated/reinstalled the guilty one.
>
> There's sysutils/bsdadminscripts, which provides pkg_libchk: that's a
> tool for checking if any port misses a shared library. It has been
> rather helpful back when I was using portupgrade...
>
> Regards,
> Christoph
>

I believe bsdadminscripts has been withdrawn. You should use "pkg check -B"
to check.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Binary update to -STABLE? And if so, what do I get?

[Kevin Oberman]

On Thu, Feb 14, 2019 at 3:10 AM Pete French 
wrote:

>
>
> On 14/02/2019 01:43, Jason Tubnor wrote:
> > I also have hit this IPv6 issue (I thought I was going crazy until I
> worked
> > it out) and other iflib issues in 12.0, which have been fixed in -STABLE
> > that really should be patched in 12.0 or bring forward an early 12.1
> > release. For our use case, 12.0 is just too buggy for production at this
> > rate and we won't touch it, which is a shame because there is a lot of
> good
> > work in there that we would like to use but it is trumped by the
> breakages.
>
> Any reason behind not running STBLE out of interest ? Yes, 12 has been
> buggy with regards to networking, but these things get fixed very fast
> and I now have all my machines on the lattest STABLE in production, as
> of yesterday.
>
> -pete.
>

Generally, not many.

Far and away the biggest is the requirement to build from sources. It's not
a big deal for me, but if I still had many systems to deal with, that would
be a pain.

I might also mention that just before the pre-release freeze and after a
release, STABLE and be a bit unstable as developers rush to get things in
before the freeze or to add things that they did not want to MFC with
little test time before a release. In recent years this issue has
significantly improved, though.

I run either HEAD or STABLE on my personal system and RELEASE on my only
server, the latter just so I can do binary updates. My server is on hold at
11.2 due to the IPv6 issue and I am amazed that this BIG oops did not
result in an EN and a patched release. Lack of IPv6 is not, for many
people, a minor issue.

The bottom line is that the only real reasons I see for not running stable
is the lack of binary updates, and issues with systems being slightly out
of sync if all are not updated to the same SVN revision at all times. Those
are very big reasons for many.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: More CARP issues under 12

[Kevin Oberman]

On Thu, Jan 17, 2019 at 4:21 AM Pete French 
wrote:

> so, having got a workaround for yesterdays problems, I now went to upgrade
> my
> other pair of boxes using CARP. No 'pf' on these, just one shared address.
> This is the setup I have tested in development and it works fine.
>
> I install the new kenel and do the first reboot - and I get the panic
> below. Maybe its not carp related, but seems suspicious as the last
> thing it spits out is a carp message.
>
> Note this is the first reboot - so 12.0 kernel with the 11 userland, in
> perparation for the installworld step. Machine is booting from, ZFS and
> also
> has a GELI partition contain some data which requires a manual password.
>

To point  out the obvious, booting a 12.0 kernel with 11  userland to
multiuser mode is seriously unsupported. You really need to boot to single
user and install 12.0 userland to really expect things to work. OTOH, while
I would expect that MANY things might not work, panics should not come from
problems in userland. Still, I would not be at all shocked if it turns out
to be coincidental to CARP. I would also not be shocked if this makes no
difference, but even between minor version updates, there can be issues
when the kernel and userland are different versions.

Is there a reason that a standalone boot is not possible? Both installworld
and mergemaster should be run before moving to multiuser mode and reboot is
preferred to exit. In some cases even delete-old can be required before
safely going to multimode.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: USB disks dropping off-line

[Kevin Oberman]

On Sat, Jan 12, 2019 at 9:12 AM Barney Wolff  wrote:

> I've had what may be the same problem for years, with a USB3 disk, on both
> 10-stable and 12.0-release. I've never found a cause, though power gitches
> might be responsible. As a pragmatic fix I have the backup disk as a zpool
> and run a daemon that simply does a zpool clear if it finds the pool
> unhealthy during the backup. That lets the backup complete every time - the
> pool is set to wait on error, so having the daemon check once a minute
> works with minuscule overhead.
>
> On Fri, Jan 11, 2019 at 11:31:55PM -0800, Kevin Oberman wrote:
> > Cue Twilight Zone theme. For your consideration: This started in
> December
> > when I was running 11.2-STABLE. Starting in December, when I try to
> backup
> > my laptop to a USB drive, it periodically dropped off-line (disconnected)
> > and immediately reconnected. This was originally using rsync. It seemed
> > fairly random and, eventually I got a successful backup. After I upgraded
> > to 12.0, it was much worse and I could no longer get a clean rsync.
> >
> > I assumed that the drive was failing and swapped it for an identical one,
> > re-partitioned, and used dd to copy each partition. The same thing
> > happened, but I noticed that it seemed to happen when the system was a
> bit
> > active. I then shutdown X and tried with nothing else running. It ran
> for a
> > few minutes until I did a sync from a different login while the dd was
> > running. Boom. Disk disconnected again.
> >
> > I finally got an almost complete backup of /usr. I had about 1-2 GB lest
> > when it happened again. I suspect that some background operation
> (periodic
> > sync?) triggered it again.
> >
> > Any suggestions?
> >
> > Here is my system info: Lenovo T520 now running FreeBSD 12.0-STABLE
> r342788
> > and GENERIC config except SCHED_4BSD. System is completely stable except
> > for the USB disk dropping off-line. Disk is a 2TB WD My Passport. It is a
> > USB 3.0 drive,but plugged intoa 2.0 port. (The T520 has no 3.0
> capability.
> >
> > Has anyone seen anything like this? Any ideas? I am REALLY nervous
> running
> > without a backup.
>

I have now confirmed that the dd runs with no issues when run in
stand-alone mode. As long as the system makes no other disk access, it
appears that the disk runs fine.  I will drop back to single-user and dd my
media (mostly music including music videos) later today and my 600 GB bulk
data disk overnight tonight. At about an hour per 100 gig, it will take a
while. I expect all to runs cleanly and I wish I had a USB3 port on this
system!
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

USB disks dropping off-line

[Kevin Oberman]

Que Twilight Zone theme. For your consideration: This started in December
when I was running 11.2-STABLE. Starting in December, when I try to backup
my laptop to a USB drive, it periodically dropped off-line (disconnected)
and immediately reconnected. This was originally using rsync. It seemed
fairly random and, eventually I got a successful backup. After I upgraded
to 12.0, it was much worse and I could no longer get a clean rsync.

I assumed that the drive was failing and swapped it for an identical one,
re-partitioned, and used dd to copy each partition. The same thing
happened, but I noticed that it seemed to happen when the system was a bit
active. I then shutdown X and tried with nothing else running. It ran for a
few minutes until I did a sync from a different login while the dd was
running. Boom. Disk disconnected again.

I finally got an almost complete backup of /usr. I had about 1-2 GB lest
when it happened again. I suspect that some background operation (periodic
sync?) triggered it again.

Any suggestions?

Here is my system info: Lenovo T520 now running FreeBSD 12.0-STABLE r342788
and GENERIC config except SCHED_4BSD. System is completely stable except
for the USB disk dropping off-line. Disk is a 2TB WD My Passport. It is a
USB 3.0 drive,but plugged intoa 2.0 port. (The T520 has no 3.0 capability.

Has anyone seen anything like this? Any ideas? I am REALLY nervous running
without a backup.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Congratulations on the Silver Anniversery Edition of FreeBSD

[Kevin Oberman]

I worked with 4.2BSD and 4.3BSD back in the 70s and 80s. I moved to other
OSes (Digital RT, RSX and VMS an Varian Vortex) and returned in about 1999
to FreeBSD 3.0. I've been using FreeBSD ever since. It's been wonderful and
I am so grateful to all of the people who have keeping it going over the
years. I try to contribute when I can, but I am not a coder, so it's in
other ways.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


On Wed, Dec 12, 2018 at 6:21 AM Pete French 
wrote:

> > Glen,
> >   It is just a bit shy of 25 years and 1 month that I shipped
> > the 1.0 Release.  Its been a long road, but we are here now!
>
> Its alwasy really nice to see poeple who have been with the project since
> the start still around :-) So, time to start upgrading everything to 12.0!
>
> well done to all involved...
>
> -pete.
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: TouchPad Synaptic on ThinkPad x280

[Kevin Oberman]

On Wed, Nov 21, 2018 at 3:12 AM Jacques Foucry 
wrote:

> Hello,
>
> After my little presentation, it's time for me to ask you some question.
>
> 1/ I run FreeBSD 11.2-Release P4 on a ThinkPd lenovo X280
>
> # uname -rms
> FreeBSD 11.2-RELEASE-p4 amd64
>
> 2/ The touchpad run well with synaptic driver
>
> # dmesg | grep -i touchpad
> psm0: model Synaptics Touchpad, device ID 0
>
> The only thing very annoying is that I can't find the right way to
> disable the touchpad since I use the keyboard.
>
> [...]


> Is it a no-feature on synaptic driver?
>
# sysctl hw.psm.synaptics.touchpad_off=1
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: dmesg submission service -- please submit today

[Kevin Oberman]

Warner said that he would look at submissions in about a month. "I'll be
using the data in about a month to look at old parallel scsi driver use."

He's looking for information on what drivers are still needed, so only if
the SCSI drives require in different drivers (unlikely) would that be
needed. I suspect that, unless you use CardBus type stuff, just the
/var/run/dmesg.boot should be all that i required.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


On Sun, Oct 7, 2018 at 10:11 AM Roderick  wrote:

>
> On Sat, 6 Oct 2018, Warner Losh wrote:
>
> > As you can tell, the project is looking to clear some of the deadwood
> from
> > its driver lists. One problem is that we have to guess what's in used
> based
> > on our personal experience. This has proven to be less reliable than
> hoped
> > in the 10/100 discussions that are going on now.
>
> Should I dump a dmesg with any device I have connected to every computer
> I have? Deadline today?
>
> Or better I risk not be able to read data on old SCSI discs I am not
> using now?
>
> Best regards
> Rodrigo
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD 11.1-RELEASE-p13 fatal trap 12: page fault while in kernel mode

[Kevin Oberman]

On Sun, Sep 9, 2018 at 3:59 AM Rainer Duffner 
wrote:

>
>
> > Am 09.09.2018 um 11:08 schrieb Eugene Grosbein :
> >
> > This list strips attachments, so you should upload it somewhere and post
> a link.
>
>
>
> Well actually, the text you get when you post one says it’s awaiting
> moderator approval.
>
> But I found a way to upload it without signing up for some site:
>
> https://ibb.co/nHK9LU
>

Actually, what gets stripped is attachments that are not text/plain.
"text/plain gets through just fine.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: How do I stop using local_unbound ?

[Kevin Oberman]

On Mon, Aug 6, 2018 at 7:57 AM, John Kennedy  wrote:

> On Mon, Aug 06, 2018 at 03:06:00PM +0100, Pete French wrote:
> > having enabled local_unbound in /etc/rc.d how do I remove that
> > and go back to using just DHCP delivered nameservers ? I
> > set it to 'NO' but yet the machine still seems to have traces of
> > the config in other places and keeps trying to use them, for reasons I
> > dont understand.
> >
> > Is there a quyick guide to clearing this off a system when you dont want
> to use
> > it anymore ? I get that it needs to be slightly complex to do what it
> does,
> > but its proving very hard to fix the broken DNS looksup!
>
> Hmm.  First, make sure that it isn't running (service local_unbound stop,
> etc).
> Then look at your /etc/resolv.conf -- unbound tends to rewrite that on
> initial
> startup, taking some of it's settings and inserting itself into the middle
> as a
> caching DNS server.  At the very least, you want something like this:
>
> nameserver 8.8.8.8
>
> I think the default DHCP client stomps all over /etc/resolv.conf fairly
> well,
> but see what options are in there (for example, options for
> domain-name-servers
> and domain-name).  The stock /etc/dhclient.conf is all comments.
>
> I have issues with the DNS results my ISP returns to me, but setting up a
> cache
> or using sites like 8.8.8.8 (google public DNS, if you don't mind feeding
> the
> beast) fixes that.
>

If you don't want to feed the beast, maybe 9.9.9.9 (Quad9). You can read
about it at:
https://arstechnica.com/information-technology/2017/11/new-quad9-dns-service-blocks-malicious-domains-for-everyone/
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Does VirtualBox's vboxnetflt(4) work on stable/11 | 11.2?

[Kevin Oberman]

On Tue, Jun 19, 2018 at 11:30 AM, Harry Schmalzbauer 
wrote:

> Am 16.06.2018 um 21:42 schrieb Harry Schmalzbauer:
> …
>
>> To rule out a known vboxnetflt(4) limitation/failure, I'd like to know if
>> somebody successfully uses vboxnetflt(4) from virtualbox-ose-kmod-5.2.12 on
>> stable/11|11.2.
>>
>
> Really nobody out there who has VirtualBox sucessfully running under
> stable/11 or 11.x with bridged network?
>
> Anyone who tried, but also observed similar problems like I have on
> -current?
>
> Thanks,
>
> -harry
>

I suspect you would have gotten better response if you had asked for
someone using a bridged network (as opposed to NATed) on VirtualBox 5.2.12
ib FreeBSD-11. I had to check on just what vboxnetflt was to realize that,
yes, I use it and it works fine on my 11-STABLE system system. Worked on 11
from the time 5.12 was placed in ports ubtil now on several different
revisions of STABLE.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: lightly loaded system eats swap space

[Kevin Oberman]

On Mon, Jun 18, 2018 at 5:27 AM, tech-lists  wrote:

> On 18/06/2018 09:08, Erich Dollansky wrote:
>
>> Hi,
>>
>> On Sun, 17 Jun 2018 23:19:02 +0100
>> tech-lists  wrote:
>>
>> freebsd-11-stable r333874, ZFS raidz1-0 (3x4TB disks), 128GB RAM,
>>> Swap: 4096M Total, 3502M Used, 594M Free, 85% Inuse
>>>
>>
>> this might not be related but I noticed that your swap space is small
>> compared to RAM size. I noticed on a much smaller Raspberry Pi, that it
>> runs into trouble when there is no swap even there is enough RAM
>> available. Is it easily possible for you to add some GB of swap space
>> and let the machine run then?
>>
>> How much swap do the other machines have?
>>
>
> Hi,
>
> Yes, the machine with the problem uses the default 4GB swap. That's all
> the swap it has. The machine without issue has a swapfile installed on a
> SSD in addition to the default 4GB swap.
>
> problematic machine:
> Device  512-blocks UsedAvail Capacity
> /dev/ada0p38388608 3.3G 714M83%
>
> machine without a problem, it has swapfile installed:
> Device  512-blocks UsedAvail Capacity
> /dev/ada0s1b   8262248 1.7G 2.2G44%
> /dev/md0  65536000 1.9G  29G 6%
> Total 73798248 3.7G  32G10%
>
> I added the swapfile a long time ago on this machine due to the same issue.
>
> But my problem isn't so much an out of swapspace problem; all this is, is
> a symptom. My problem is "why is it swapping out at all on a 128GB system
> and why is what's swapped out not being swapped back in again".
>
> thanks,
> --
> J.


Small correction. Your problem is  "why is it swapping out at all on a
128GB system ." Once pages are swapped out, they are never swapped back in
until/unless they are needed. There is no reason to waste time/disk
activity to swap pages back into memory unless they are required. RAM is
always more valuable than swap.

Ir is easy to write a process that eats up a large amount of memory, then
goes idle without freeing it. The memory will get pages out, fill swap,
and, unless the process terminates or becomes active, will consume up a
great deal of swap space "forever". Firefox is a good example of this. I
have to restart it every day or two and occasionally will run out of swap
which results in a nearly deadlocked system. It can take many minutes to
just kill firefox.
-- 
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

PRERELEASE back?

[Kevin Oberman]

After teh announcement of RC1 I updated my 11-STABLE box, expecting wither
that I would see RC1 or STABLE, depending on whether the 11.2 BRANCH had
been created, but instead I am "back" at 11.2-PRERELEASE #1.

Is this intentional? At least it is confusing.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD 11.2-BETA3 Kernel Panic (Page Fault) when loading kernel module "vboxdrv.ko"

[Kevin Oberman]

See my response of a few minutes ago the another report of this issue.

Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Suspected KBI breakage between FreeBSD 11.1-p9 and FreeBSD 11.2-BETA3

[Kevin Oberman]

On Thu, May 31, 2018 at 3:43 AM, Ka Ho Ng  wrote:

> Hi folks,
>
> After an upgrade from 11.1-p9 to 11.2-BETA3, vboxdrv and nvidia no longer
> works. `kldload vboxdrv` will throw kernel panic immediately.
>
> Here are the corresponding bugzilla tickets:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228536
>
> Since these two kmod work after rebuilding the package, I suspect the issue
> is due to KBI breakage.
>
> Could anyone take a look into the issue?
>
> Thanks,
> Ka Hothe BETA
>

This is a long-standing issue with ports that build kernel modules,
especially virtualbox-ose-kmod. nvidia has also been touched by this,
though not as often. Kernel modules are part of the kernel and often make
use of variables in the in kernel memory that are not part of the formal
KBI. (sysutils/lsof is not a kernel module, but has many of the same issues
and the documentation clearly states that the kernel sources at port build
time MUST match the running kernel.)

It has long been suggested that any port that installs a kernel module be
added to PORTS_MODULES in /etc/src.conf so that they will be rebuilt
whenever a kernel is built This does not play well with packages during the
release cycle for a new FreeBSD version, as the packages for he modules
will lag behind BETA builds. The only way I see around this is to have full
kernel sources available and manually build the modules for BETA releases.
packages are rebuilt for the actual release, so this problem only impacts
systems running STABLE or CURRENT.

Perhaps a policy of generating new packages for the small number of ports
where this is an issue for each BETA and RC would fix it of logistical
issues are tractable.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Upgrade to 11.2-BETA1: vboxdrv kernel modulo load leads to panic unless vbox ports be rebuilt

[Kevin Oberman]

On Sun, May 13, 2018 at 12:41 PM, Jose G. Juanino <jjuan...@gmail.com>
wrote:

> On Sunday, May 13 at 15:53:28 CEST, Jose G. Juanino wrote:
> > Hi FreeBSD stable,
> >
> > I have upgraded from 11.1 to 11.2-BETA1 right now. I use Virtualbox to
> > run Windows 7 from the FreeBSD box, and just after to complete the
> > upgrade and reboot, the system panics just after to load kernel module
> > vboxdrv.
> >
> > The workaround is rebuild both emulators/virtualbox-ose and
> > emulators/virtualbox-ose-kmod ports from within 11.2-BETA1, and
> > after that everything works nicely as before the upgrade. I hope this
> > help other people suffering a similar issue. Best regards.
>
> Full backtrace:
>
> https://pastebin.com/raw/17UU5Mij
>
>
> --
> Jose G. Juanino


Kernel modules are NOT guaranteed to work between kernels. It is
recommended that all kernel modules from ports and lsof be added to
PORTS_MODULES so they are re-built after each kernel update. Rebuild
virtualbox-ose-kmod, unload all vbox modules and reload them. That should
fix he problem.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: kern.sched.quantum: Creepy, sadistic scheduler

[Kevin Oberman]

On Mon, Apr 16, 2018 at 11:56 PM, Eivind Nicolay Evensen <
eivi...@terraplane.org> wrote:

> On Wed, Apr 04, 2018 at 09:32:58AM -0400, George Mitchell wrote:
> > On 04/04/18 06:39, Alban Hertroys wrote:
> > > [...]
> > > That said, SCHED_ULE (the default scheduler for quite a while now) was
> designed with multi-CPU configurations in mind and there are claims that
> SCHED_4BSD works better for single-CPU configurations. You may give that a
> try, if you're not already on SCHED_4BSD.
> > > [...]
> >
> > A small, disgruntled community of FreeBSD users who have never seen
> > proof that SCHED_ULE is better than SCHED_4BSD in any environment
> > continue to regularly recompile with SCHED_4BSD.  I dread the day when
> > that becomes impossible, but at least it isn't here yet.  -- George
>
> Indeed 4bsd is better in my case aswell. While for some unknown to me
> reason
> ule performed a bit better in the 10.x series than before, in 11.x
> it again is in my case not usable.
>
> Mouse freezes for around half a second with even frequency by just moving
> it around in x11. Using 4bsd instead makes the problem go away.
> I'm actually very happy that ule became worse again because going
> back to 4bsd yet again also gave improved performance from other
> dreadfully slow but (to me) still useful programs, like darktable.
>
> With 4bsd, when adjusting shadows and highlights it is possible to see
> what I
> do when moving sliders. With ule it has never been better than waiting
> 10-20-30 seconds to see where it was able to read a slider position
> and update display, when working on images around 10500x10500 greyscale.
>
> It's not single cpu/single core either:
> CPU: AMD FX(tm)-6300 Six-Core Processor  (3817.45-MHz K8-class
> CPU)
>
>
>
>
> --
> Eivind
>

My experience has long been that 4BSD works far better for interactive, X
based systems than ULE. Even on 10 I saw long, annoying pauses with ULE and
I don't se those with 4BSD. I'd really like to see it better known that
this is often the case. BTW, my system is 2 core/4 thread Sandybridge.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: KBI unexpexted change in stable/11 ?

[Kevin Oberman]

On Wed, Mar 28, 2018 at 9:46 AM, Gary Palmer <gpal...@freebsd.org> wrote:

> On Wed, Mar 28, 2018 at 11:16:49AM -0500, Eric van Gyzen wrote:
> > On 03/28/2018 10:35, Slawa Olhovchenkov wrote:
> > > On Wed, Mar 28, 2018 at 10:29:10AM -0500, Eric van Gyzen wrote:
> > >
> > >> On 03/28/2018 08:09, Slawa Olhovchenkov wrote:
> > >>> I am upgrade system to latest -STABLE and now see kernel crash:
> > >>>
> > >>> - loading virtualbox modules build on 11.1-RELEASE-p6
> > >>> - loading nvidia module build on 11.1-RELEASE-p6 and start xdm
> > >>>
> > >>> Is this expected? I am mean about loading modules builded on
> > >>> 11.1-RELEASE on any 11.1-STABLE.
> > >>
> > >> This is not expected.  Can you bisect to find the stable/11 commit
> that
> > >> broke this?
> > >>
> > >> If you can roll back to 11.1-RELEASE, you could probably just
> > >> buildkernel and installkernel from various points along stable/11.
> That
> > >> would save a lot of time by avoiding buildworld.
> > >
> > > r325665 is previos point and is good.
> > > r331615 crashed.
> > > Can I use some script for bisect?
> >
> > I'm not aware of a script for this.  The only tool I've used is "git
> > bisect", which is very handy if you're already familiar with git.
>
> You may want to try devel/p5-App-SVN-Bisect.  Never used it, so
> no idea if it's functional or helpful, just found it doing a quick
> search
>
> Regards,
>
> Gary
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>

Regardless of intent, updates to port based modules can and and will break
when the kernel is updated. lsof breaks quite often, as well. It touches
things in the kernel that are intended for internal use only, so that is to
be expected. I can't say that virtualbox-ose-kmod has had to be rebuilt
because I put it into PORTS_MODULES a couple of years ago after having it
fail on several occasions. Every time it gets broken again thee are lots of
threads in STABLE like this one.

It would be nice if this could be fixed, but it is the case.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Calling nxge(4) users

[Kevin Oberman]

On Sun, Mar 25, 2018 at 11:40 AM, Brooks Davis <bro...@freebsd.org> wrote:

> The nxge(4) driver for the Neterion Xframe-I and Xframe-II 10GbE
> adapters has obvious bugs (by inspection) and it doesn't appear the
> company exists any more.  We'd like to see if there are any significant
> users of this device and plan to remove it from FreeBSD-12 if not.
>
> -- Brooks
>

Just for the record, Neterion was acquired by Exar, an old-line hybrid IC
company in 2010 and Exar was acquired last year by MaxLinear. Looks like
Exar bought them for some of their tech and killed off the Ethernet
products.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [CFT] [X11] graphics/drm-next-kmod now builds, loads and works on FreeBSD-11-stable

[Kevin Oberman]

On Sun, Feb 18, 2018 at 2:36 PM, Hans Petter Selasky <h...@selasky.org>
wrote:

> On 02/18/18 23:27, Kevin Oberman wrote:
>
>> On Sun, Feb 18, 2018 at 12:35 PM, Hans Petter Selasky <h...@selasky.org>
>> wrote:
>>
>> Hi FreeBSD desktop users!
>>>
>>> During the past week and over the weekend all parts needed for building,
>>> loading and using graphics/drm-next-kmod on FreeBSD-11-stable have been
>>> completed!
>>>
>>> A big thanks to all the people contributing to graphics support under
>>> FreeBSD in both kernel and user-space! You'll find their names in the
>>> commit logs including myself :-)
>>>
>>> Links:
>>> https://www.freshports.org/graphics/drm-next-kmod
>>> https://svnweb.freebsd.org/changeset/base/329527
>>>
>>> Issues are reported here:
>>> https://github.com/FreeBSDDesktop/kms-drm/issues
>>>
>>> --HPS
>>>
>>>
> Hi Kevin,
>
>
>> Wow! That is awesome. Thanks to all of the contributors.
>>
>
> Thank you!
>
>
>> Any instructions? Am I right that the mod setting driver should generally
>> be used. None of the links above really covers implementation.
>>
>
> I believe the package when you install it will give you some instructions
> in the pkg-message.
>
> Basically:
>
> portsnap fetch update
>
> Make sure your kernel sources in /usr/src .
> cd /usr/src
> make buildkernel -jX
> make installkernel -jX
>
> cd /usr/ports/graphics/drm-next-kmod
> make all install clean
>
> Edit /etc/rc.conf and add for example:
>
> kld_list="i915kms"
>
> Then reboot and twin your thumbs.
>
> If it fails goto single user mode.
>
> mount -a
>
> Edit /etc/rc.conf and remove the kld_list=...
> Save and type exit.
>
> Before starting X.org you should have the correct xf86-video-xxx drivers
> installed, because then 2D and 3D acceleration will activate.
>
> A quick tip for tear-free video with intel drivers:
>
> cat /usr/local/etc/X11/xorg.conf.d/20-intel.conf
> Section "Device"
>Identifier  "Device0"
>Driver "intel"
>Option "AccelMethod" "sna"
>Option "TearFree" "true"
> EndSection
>
> --HPS
>

Thanks, Hans! I should have looked at the message file. It explained most
of it, though I especially appreciate the tearfree config as I am using
Intel graphics.

This is also the first I have seen of modular config files. Guess I have
some man page reading to do.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [CFT] [X11] graphics/drm-next-kmod now builds, loads and works on FreeBSD-11-stable

[Kevin Oberman]

On Sun, Feb 18, 2018 at 12:35 PM, Hans Petter Selasky <h...@selasky.org>
wrote:

> Hi FreeBSD desktop users!
>
> During the past week and over the weekend all parts needed for building,
> loading and using graphics/drm-next-kmod on FreeBSD-11-stable have been
> completed!
>
> A big thanks to all the people contributing to graphics support under
> FreeBSD in both kernel and user-space! You'll find their names in the
> commit logs including myself :-)
>
> Links:
> https://www.freshports.org/graphics/drm-next-kmod
> https://svnweb.freebsd.org/changeset/base/329527
>
> Issues are reported here:
> https://github.com/FreeBSDDesktop/kms-drm/issues
>
> --HPS
>

Wow! That is awesome. Thanks to all of the contributors.

Any instructions? Am I right that the mod setting driver should generally
be used. None of the links above really covers implementation.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: stable/11 r329462 - Meltdown/Spectre MFC questions

[Kevin Oberman]

On Sat, Feb 17, 2018 at 12:38 PM, Pete French <petefre...@ingresso.co.uk>
wrote:

>
>
> On 17/02/2018 20:19, Matt Smith wrote:
>
> And thank you for pointing this out. I can now just wait a while to see
>> what comes along rather than accidentally upgrading it and killing the
>> already really slow performance.
>>
>> I was just looking at this too, and wondering what (if any) the
> performance impact is on FreeBSD. I had a quick google to see if I could
> fine anything on current about it, but no luck. Anyone done any
> measurements ?
>
> -pete.


Well, I would also like a bit of information on this. When I get a moment
I'll see if I can find anything on this on the current@ archive.

Looks like all are loadables, so need to be defined in /boot/loader.conf
and can only be changed on a boot  with the exception of hw.ibrs_disable
which is settable either at boot or via sysctl. Looks like that is the one
to twiddle to check on impact.

I'm currently updating my stable system as this hit the tree after my
morning updates.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: error instaling any ports

[Kevin Oberman]

On Wed, Oct 18, 2017 at 3:12 AM, Denis Granato <denisgran...@gmail.com>
wrote:

> thanks guys , I will try and let you know
> about the kernel, I think was for ipfw or something
>

No need for a custom kernel for this. If you configure ipfw in rc.conf as
per the Handbook (29.4), it will load the module and your configuration
using the GENERIC kernel.

I might also point out that use of freebsd-update does NOT require that you
run a GENERIC kernel. This is discussed in the Handbook (23.2). You MUST
have a copy of the GENERIC kernel, either as your boot kernel or by placing
a copy of the GENERIC kernel in /boot/GENERIC. (N.B. This is a file name,
not a directory.) This does require rebuilding your custom kernel after the
update is otherwise complete.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683

>
>
>
> On Tue, Oct 17, 2017 at 5:11 PM, Kurt Jaeger <li...@opsec.eu> wrote:
>
> > Hi!
> >
> > > > uname -a
> > [...]
> > > > *server# uname -aFreeBSD server.avgroup.loc 9.1-PRERELEASE FreeBSD
> >
> > So you have a PRERELEASE version and you have a custom kernel.
> >
> > Do you know why that is ? Any specific change that needs to
> > be in that kernel config ?
> >
> > Please check if you have a 'svn' binary somewhere, because it looks
> > like you need to do a source upgrade first.
> >
> > rm -rf /usr/obj /usr/src
> > mkdir /usr/src
> > cd /usr/src
> > svn checkout https://svn.freebsd.org/base/release/9.3.0/ .
> > make buildworld
> > make buildkernel
> > make installkernel
> > make installworld
> > mergemaster -UiP
> > shutdown -r now
> > cd /usr/src
> > make check-old
> > make delete-old
> > make delete-old-libs
> >
> > > *server# freebsd-update -r 9.3-RELEASE upgradeLooking up
> > update.freebsd.org
> > > <http://update.freebsd.org> mirrors... 3 mirrors found.Fetching public
> > key
> > > from update6.freebsd.org... failed.Fetching public key from
> > > update5.freebsd.org... failed.Fetching public key from
> > > update4.freebsd.org... failed.No mirrors remaining, giving up*
> >
> > Well, freebsd-update only works on GENERIC kernels and systems, so
> > your first step needs to be a source upgrade.
> >
> > Please note: Your binaries from 9.1-PRE will work on 9.3, and probably on
> > 10.x, so no need to worry about the packages installed for now.
> >
> > You can rebuild your ports when you're on 10.x.
> >
> > --
> > p...@opsec.eu+49 171 3101372 3 years
> to
> > go !
> >
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: TSC timekeeping and cpu states

[Kevin Oberman]

On Mon, Aug 14, 2017 at 8:38 AM, Ian Smith <smi...@nimnet.asn.au> wrote:

> On Mon, 14 Aug 2017 17:16:22 +1000, Aristedes Maniatis wrote:
>
>  > On 14/8/17 3:08PM, Kevin Oberman wrote:
>  > > Again, the documentation lags reality. The default was changed for
>  > > 11.0. It is still conservative. In ALMOST all cases, Cmax will yield
>  > > the bast results. However, on large systems with many cores, Cmax
>  > > will trigger very poor results, so the default is C2, just to be
>  > > safe.
>
> Given it's a server, anything beyond C2 is likely not worth trying.
> OTOH, C2 is perhaps not worth avoiding; it's probably low latency and
> should result in lower power consumption, so heat, and unlikely to hurt.
>
> Or at least, I suspect that's the case .. cc'ing Alexander, as the wiki
> article you referenced was his doing, so he's among those best placed.
>
>  > > As far as possible TSC impact, I think older processors had TSC
>  > > issues when not all cores ran with the same clock speed. That said,
>  > > I am not remotely expert on such issues, so don't take this too
>  > > seriously.
>
> I wasn't aware that FreeBSD could yet do different freqs on different
> cores?  But I'm less expert than Kevin, and certainly behind the times.
>
>  > Thanks Kevin
>  >
>  > What does 'large' and 'many cores' mean here? Is 24 cores large or
>  > small? For a server do we ever want the CPU to enter states other
>  > than C1?
>
> If C2 works well on your box, I don't see why you wouldn't want to use
> it .. but others might.  I have no personal experience beyond 2 cores,
> but I'm perennially curious about such issues, as Kevin knows :)
>
> Are you using powerd?  And what says, for example:
>
>  sysctl -a | egrep 'cx|available|_freq|freq_|choice' | grep -v net\.
>
> which should include your timecounter and eventtimer setup too.
>
> cheers, Ian
>

I guess I need to clarify. No, FreeBSD does not have the ability to tun
different cores at different frequencies. I seem to recall that TCC on some
processors could adjust the frequency of a core exceeding a defined
temperature, skipping N of every 8 clock cycles to slow the processor and
reduce the temperature. This is what TCC was designed for. It is entirely
possible that I am not correctly remembering the details of the issue, but
it could only be resolved by switching from TCC to another clocking system.

If memory serves, and it may not, there was an issue a few years ago (jhb@
worked the issue) where TSC was varying with frequency and that caused
clock drift. I believe all "modern" processors do not have this issue and
it seems unlikely that any system running 24 cores is old enough that this
might be an issue.

Sorry for any confusion I may have caused.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: TSC timekeeping and cpu states

[Kevin Oberman]

On Sun, Aug 13, 2017 at 8:25 PM, Aristedes Maniatis <a...@ish.com.au> wrote:

> I note that in FreeBSD 11, we now have this:
>
> # grep performance_cx_lowest /etc/defaults/rc.conf
> performance_cx_lowest="C2"  # Online CPU idle state
>
> However this wiki page suggests that C1 is the default
>
> https://wiki.freebsd.org/TuningPowerConsumption
>
>
> Are these inconsistent?
>
>
> I went looking for this because I've been having trouble with the TSC-low
> timecounter hardware choice and my system clock running at about 80% of
> normal speed. Moving to ACPI-fast solved this problem.
>
> Could the power saving CPU states be related to this problem, or should I
> look elsewhere for the TSC issue?
>
> This is a server, not a laptop.
>
>
> Thanks
> Ari
>
>
>
> --
> -->
> Aristedes Maniatis
> CEO, ish
> https://www.ish.com.au
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>

Again, the documentation lags reality. The default was changed for 11.0. It
is still conservative. In ALMOST all cases, Cmax will yield the bast
results. However, on large systems with many cores, Cmax will trigger very
poor results, so the default is C2, just to be safe.

As far as possible TSC impact, I think older processors had TSC issues when
not all cores ran with the same clock speed. That said, I am not remotely
expert on such issues, so don't take this too seriously.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Program crashes after 320666

[Kevin Oberman]

multimedia/avidemux_qt4 has started dumping core with segfaults and other
errors in libthread called from Qt4. I am suspicious that the real problem
is in Qt4 and those errors were previously not detected and usually not
causing a problem.

The problem shows up with kernels at r320666 and later. The update on July
5 was:
Add MAP_GUARD and use it for stack protection.

Should I open a ticket for the Qt4 or should I spend more effort on whether
it might be a kernel issue. (Pretty sure it's Qt4 at fault.) I might also
look into updating the port to use Qr5 as Qt4 is clearly starting to bitrot
and support for Qt5 has already been added upstream.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: issues with powerd/freq_levels

[Kevin Oberman]

On Mon, Jul 31, 2017 at 3:48 AM, Ian Smith <smi...@nimnet.asn.au> wrote:

> On Mon, 31 Jul 2017 10:09:11 +0300, Daniel Braniss wrote:
>
>  > I am trying out PCengines latest apu2 boards, and I just noticed that
> with different Freebsd versions I get
>  > different freq_levels, and so when idling, each box (have 5) has a
> different freq/temperature value, ranging
>  > from 125/69.1C, 600/59.0C to 75/56.0C
>  >
>  > FreeBSD apu-4 11.1-STABLE FreeBSD 11.1-STABLE #5 f565b5a06ab3 (11) tip:
> Mon Jul 31 09:36:33 IDT 2017
>  > apu-4# sysctl dev.cpu.0.freq_levels
>  > dev.cpu.0.freq_levels: 1000/980 800/807 600/609
>
> That looks about right.  On a Core2Duo (still on 9.3) I get:
> dev.est.1.freq_settings: 2401/35000 2400/35000 1600/15000 800/12000
> dev.est.0.freq_settings: 2401/35000 2400/35000 1600/15000 800/12000
> dev.cpu.0.freq_levels: 2401/35000 2400/35000 1600/15000 800/12000
> dev.cpu.0.freq: 800
>
> But only because I'd added to /boot/loader.conf:
>
> hint.p4tcc.0.disabled=1
> hint.acpi_throttle.0.disabled=1
>
> which became the defaults sometime, maybe not before 11.0?  Otherwise
> mine would look more similar to the one below, with all 12.5% increments
> in frequency enabled, which doesn't actually save any power at all.
>
>  > FreeBSD apu-5 11.1-PRERELEASE FreeBSD 11.1-PRERELEASE #0 21e9d1ca9b80
> (11) tip: Tue May 30 11:51:48 IDT 2017
>  > apu-5# sysctl dev.cpu.0.freq_levels
>  > dev.cpu.0.freq_levels: 1000/966 875/845 800/795 700/695 600/600 525/525
> 450/450 375/375 300/300 225/225 150/150 75/75
>
> Looks like either p4tcc or acpi_throttle is enabled?  See cpufreq(4).
> As above, these don't buy you anything but extra busyness for powerd.
>
> Also noticed that the (nice, low!) milliwatt figures for 1000/800/600
> freqs are a bit different to the -stable one.  Slightly Different model?
>
>  > FreeBSD apu-1 10.3-STABLE FreeBSD 10.3-STABLE #4 267788fd852c (10) tip:
> Tue Jan 10 09:09:00 IST 2017
>  > apu-1# sysctl dev.cpu.0.freq_levels
>  > dev.cpu.0.freq_levels: 1000/-1 875/-1 750/-1 625/-1 500/-1 375/-1
> 250/-1 125/-1
>
> And that looks like est(4) isn't enabled/attaching at all .. see dmesg
> on all of these for clues.
>
>  > so, any ideas as to what is going on?
>
> Pure guesswork on experience with older versions, I'm not up to date.
>

Very odd. Are all systems running identical CPUs and BIOSes? Identical
loader and sysctl configurations? Look at /var/rn/dmesg.boot for CPU
information. Is EST being detected? It used to be early in the boot
process, but is now fairly late. (In my case, about 2/3 through the
dmesg.boot file.

I have p4tcc and throttling explicitly turned off (which should now be the
default), but my Sandy Bridge Core i5 still shows:
dev.cpu.0.freq_levels: 2501/35000 2500/35000 2000/26426 1800/23233
1600/20164 1400/17226 1200/14408 1000/11713 800/9140
The first is really bogus to indicate "turbo" mode.

Temperature is a totally separate issue. It is VERY sensitive to external
issue like airflow and position of the CPU in relation to other components
in the chassis Also, unless you have a lot of cores, you probably should
set both economy_cx_lowest and performance_cx_lowest to Cmax. Economy
should default to that, but  performance will not as that can cause issues
on systems with large numbers of cores, so is set to C2. Many such system
used to disable deeper sleep modes in BIOS, but I am way behind the times
and don't know about the current state of affairs. Certainly for systems
with 32 or fewer cores, this should not be an issue. In any case, Cx state
can sharply impact temperature.

Finally, the last case with power levels of -1 for all frequencies is
probably because the CPU manufacturer (Intel?) has not published this
information. For a while they were treating this as "proprietary"
information. Very annoying! It's always something that is not readily
available. Thi is one reason I suspect your CPUs are not identical.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: pefs not working

[Kevin Oberman]

On Thu, Jul 6, 2017 at 12:32 PM, Walther <walt...@rodconit.com> wrote:

> Hello
> Testing FreeBSD 11.1 RC1 i386 version I found the following:
> I am not able to load pefs (pefs.ko) I am not receiving an error but it
> can not be loaded
> I added pefs_load="YES" to the /boot/loader.conf and I also tried running
> kldload but it ois always failing
> Thanks
>
> Walther
>

pefs does not seem to be part of the base OS. Is it installed by a port?
And, if so, which one?

If it is installed from  port, it MUST be rebuilt when the kernel is
updated. It may be installed as a package only if you are running a RELEASE
version and release candidates are not releases, so you MUST rebuild them
from sources.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Kernel panic

[Kevin Oberman]

On Wed, Jun 21, 2017 at 2:10 PM, Efraín Déctor <efraindec...@motumweb.com>
wrote:

> Hello.
>
> I found that link too, however gjournal is disabled on all of my
> filesystems, apart from that I only have trim enabled on one of my
> filesystem but when the error happened I was writing on another filesystem.
>
> Maybe WinSCP did something that FreeBSD didnt like, I am really clueless
> about this error.
>
> If it happens again I am going to update this system like you guys have
> been suggesting.
>
> Thank you very much for your help.
>
>
> El 21/06/2017 a las 03:18 p. m., Holger Kipp escribió:
>
>> I only found the following reference:
>>
>> https://forums.freebsd.org/threads/37824/
>>
>> which contains some additional links and references, especially regarding
>> journaling and softupdates, for your error message.
>>
>> Maybe this is helpful in your case?
>>
>> Apart from that - checking if the error is still there on a supported
>> more current version like 10.3 or 11 might indeed be the better option.
>>
>> Best regards,
>> Holger
>>
>> On 21. Jun 2017, at 21:56, Steven Hartland <kill...@multiplay.co.uk> o:kill...@multiplay.co.uk>> wrote:
>>
>> Given how old 9.1 is, even if you did investigate its unlikely it would
>> get fixed.
>>
>> I'd recommend updating to 11.0-RELEASE and see if the panic still happens.
>>
>> On 21/06/2017 17:35, Efraín Déctor wrote:
>> Hello.
>>
>> Today one of my servers crashed with a kernel panic. I got this message:
>>
>> panic: cancel_mkdir_dotdot: Lost inodedep
>>
>> I was just moving some files using WinSCP and then the server crashed.
>>
>> How can I trace the root of the problem?. I check and the raid seems to
>> be ok:
>>
>> mfi0 Volumes:
>>   Id SizeLevel   Stripe  State   Cache   Name
>> mfid0 (  278G) RAID-1  64k OPTIMAL Disabled 
>> mfid1 ( 1905G) RAID-1  64k OPTIMAL Disabled 
>>
>> Thanks in advance.
>>
>> uname -a
>> FreeBSD server 9.1-RELEASE-p22 FreeBSD 9.1-RELEASE-p22 #0: Mon Nov  3
>> 18:22:10 UTC 2014 r...@amd64-builder.daemonology.net<mailto:root@amd64-
>> builder.daemonology.net>:/usr/obj/usr/src/sys/GENERIC amd64
>>
>> ___
>>
>>
>>
>> Diplom-Mathematiker
>> Holger Kipp
>> Senior Consultant   [When logistics needs SAP competence] <
>> https://www.alogis.com/>
>>
>> Fon: +49 30 436 58 114
>> Fax: +49 30 436 58 214
>> Mobil:?+49 178 36 58 114
>>  alogis AG
>> Alt-Moabit 90 B
>> 10559 Berlin
>>
>>
>> holger.k...@alogis.com  www.alogis.com<http://www.alogis.com/>
>>
>> alogis AG
>> Sitz/Registergericht: Berlin/AG Charlottenburg, HRB 71484
>> Vorstand: Arne Friedrichs, Joern Samuelson
>> Aufsichtsratsvorsitzender: Dr. Christian Volkmann
>>
>> [Besuchen Sie uns auf dem SAP EAM 2017 vom 27. - 28. Juni, Potsdam!]<
>> https://www.alogis.com>
>
>
This is probably not the issue, but I have had consistent issues using scp
and sftp to copy files to FUSE based file systems (or, possibly, just
NTFS). I have not had any issues with copies to/from UFS2 systems. I'm
guessing that your local file system is UFS2 or it would have been
mentioned. I should also mention that FUSE has had at least two versions
released since I had the problems. It's not something I do often and far
less often since I moved one of the file systems, the one I most commonly
used, to UFS2.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

USB problems after r316423 (LLVM-4.0)

[Kevin Oberman]

USB on my system (Lenovo T520-Cougar Point chipset) fails to initialize. I
have reported this in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218513

Can others running 11-STABLE at or after r316423 confirm the operation of
USB ports? It seems unlikely that I am the only one seeing this as my
system is pretty vanilla, but I have seen no other reports.

If you have such a system, can you either confirm that USB is working or
test by plugging in any USB device and seeing if it shows up or check
/var/run/dmesg for the errors reported in the ticket?

I am running GENERIC except for SCHED_4BSD. (I tried SCHED_ULE with no
change.)
CPU: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz (2491.97-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x206a7  Family=0x6  Model=0x2a  Stepping=7
Other details are in the ticket.

Thanks so much.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: No USB?

[Kevin Oberman]

I have opened https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218513 on
this issue.

Bi-section in a problem as the update to LLVM  a week ago breaks building
old kernels. Hoping I can buildworld with the current compiler and then
build the kernel. (Wonder if the new compiler could be the trigger for the
problem I'm seeing?)

Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683

On Sun, Apr 9, 2017 at 10:52 AM, Kevin Oberman <rkober...@gmail.com> wrote:

> On Sat, Apr 8, 2017 at 1:55 PM, Kevin Oberman <rkober...@gmail.com> wrote:
>
>> Today, for the first time in a couple of weeks, I plugged in a USB drive
>> to my 11-STABLE system (r316552). No device was created and usbconfig only
>> sees EHCI hubs:
>> ugen1.1:  at usbus1, cfg=0 md=HOST spd=HIGH
>> (480Mbps) pwr=SAVE (0mA)
>> ugen0.1:  at usbus0, cfg=0 md=HOST spd=HIGH
>> (480Mbps) pwr=SAVE (0mA)
>>
>> Seems like I should be seeing UHCI stuff, too. Even internal devices like
>> my webcam don't show up.
>>
>> I'm running a GENERIC kernel with the following exceptions:
>> nooptions SCHED_ULE   # ULE scheduler
>> options   SCHED_4BSD  # 4BSD scheduler
>> optionsIEEE80211_DEBUG
>>
>> I tried updating my system and that made no difference. I booted up
>> Windows and it sees the USB drive just fine.
>>
>> Any things I should try or look at to try to figure out what is
>> happening? I really want to get an image of my system before moving in
>> three days.
>>
>> This is looking more and more like a bug. I con't know why nobody else
> had seen it, but here is more information:
> Relevant limes from bot:
> ehci0:  mem 0xf252a000-0xf252a3ff irq
> 16 at device 26.0 on pci0
> usbus0: EHCI version 1.0
> usbus0 on ehci0
> ehci1:  mem 0xf2529000-0xf25293ff irq
> 23 at device 29.0 on pci0
> sbus1: EHCI version 1.0
> usbus1 on ehci1
> [...]
> usbus0: 480Mbps High Speed USB v2.0
> usbus1: 480Mbps High Speed USB v2.0
> ugen1.1:  at usbus1
> uhub0:  on usbus1
> ugen0.1:  at usbus0
> uhub1:  on usbus0
> uhub0: 3 ports with 3 removable, self powered
> uhub1: 3 ports with 3 removable, self powered
> usbus0: port reset timeout
> usbus1: port reset timeout
> uhub_reattach_port: port 1 reset failed, error=USB_ERR_TIMEOUT
> uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 1
> uhub_reattach_port: port 1 reset failed, error=USB_ERR_TIMEOUT
> uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 1
>
> usbconfig -d ugen1.1 reset produced:
> Apr  9 09:15:11 rogue kernel: uhub1: at usbus0, port 1, addr 1
> (disconnected)
> Apr  9 09:15:11 rogue kernel: uhub1:
> Apr  9 09:15:11 rogue kernel:  2.00/1.00, addr 1> on usbus0
> Apr  9 09:15:12 rogue kernel: uhub1: 3 ports with 3 removable, self powered
>
> Any ideas would be GREATLY appreciated as I can't backup or restore my
> system.
>
> I hope to boot a live version of 11-RELEASE if I can find one, and see if
> it works.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: No USB?

[Kevin Oberman]

On Sat, Apr 8, 2017 at 1:55 PM, Kevin Oberman <rkober...@gmail.com> wrote:

> Today, for the first time in a couple of weeks, I plugged in a USB drive
> to my 11-STABLE system (r316552). No device was created and usbconfig only
> sees EHCI hubs:
> ugen1.1:  at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps)
> pwr=SAVE (0mA)
> ugen0.1:  at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps)
> pwr=SAVE (0mA)
>
> Seems like I should be seeing UHCI stuff, too. Even internal devices like
> my webcam don't show up.
>
> I'm running a GENERIC kernel with the following exceptions:
> nooptions SCHED_ULE   # ULE scheduler
> options   SCHED_4BSD  # 4BSD scheduler
> optionsIEEE80211_DEBUG
>
> I tried updating my system and that made no difference. I booted up
> Windows and it sees the USB drive just fine.
>
> Any things I should try or look at to try to figure out what is happening?
> I really want to get an image of my system before moving in three days.
>
> This is looking more and more like a bug. I con't know why nobody else had
seen it, but here is more information:
Relevant limes from bot:
ehci0:  mem 0xf252a000-0xf252a3ff irq 16
at device 26.0 on pci0
usbus0: EHCI version 1.0
usbus0 on ehci0
ehci1:  mem 0xf2529000-0xf25293ff irq 23
at device 29.0 on pci0
sbus1: EHCI version 1.0
usbus1 on ehci1
[...]
usbus0: 480Mbps High Speed USB v2.0
usbus1: 480Mbps High Speed USB v2.0
ugen1.1:  at usbus1
uhub0:  on usbus1
ugen0.1:  at usbus0
uhub1:  on usbus0
uhub0: 3 ports with 3 removable, self powered
uhub1: 3 ports with 3 removable, self powered
usbus0: port reset timeout
usbus1: port reset timeout
uhub_reattach_port: port 1 reset failed, error=USB_ERR_TIMEOUT
uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 1
uhub_reattach_port: port 1 reset failed, error=USB_ERR_TIMEOUT
uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 1

usbconfig -d ugen1.1 reset produced:
Apr  9 09:15:11 rogue kernel: uhub1: at usbus0, port 1, addr 1
(disconnected)
Apr  9 09:15:11 rogue kernel: uhub1:
Apr  9 09:15:11 rogue kernel:  on usbus0
Apr  9 09:15:12 rogue kernel: uhub1: 3 ports with 3 removable, self powered

Any ideas would be GREATLY appreciated as I can't backup or restore my
system.

I hope to boot a live version of 11-RELEASE if I can find one, and see if
it works.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

No USB?

[Kevin Oberman]

Today, for the first time in a couple of weeks, I plugged in a USB drive to
my 11-STABLE system (r316552). No device was created and usbconfig only
sees EHCI hubs:
ugen1.1:  at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps)
pwr=SAVE (0mA)
ugen0.1:  at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps)
pwr=SAVE (0mA)

Seems like I should be seeing UHCI stuff, too. Even internal devices like
my webcam don't show up.

I'm running a GENERIC kernel with the following exceptions:
nooptions SCHED_ULE   # ULE scheduler
options   SCHED_4BSD  # 4BSD scheduler
optionsIEEE80211_DEBUG

I tried updating my system and that made no difference. I booted up Windows
and it sees the USB drive just fine.

Any things I should try or look at to try to figure out what is happening?
I really want to get an image of my system before moving in three days.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: slow machine, swap in use, but more than 5GB of RAM inactive

[Kevin Oberman]

On Tue, Mar 7, 2017 at 3:14 PM, Erich Dollansky <erichsfreebsdl...@alogt.com
> wrote:

> Hi,
>
> On Tue, 7 Mar 2017 23:30:58 +1100 (EST)
> Ian Smith <smi...@nimnet.asn.au> wrote:
>
> > On Tue, 7 Mar 2017 10:19:35 +0800, Erich Dollansky wrote:
> >  > Hi,
> >  >
> >  > I wonder about the slow speed of my machine while top shows ample
> >  > inactive memory:
> >
> > ( quoting from this top output because it's neater :)
> >
> >  > last pid: 85287;  load averages:  2.56,  2.44, 1.68
> >  > up 6+10:24:45 10:13:36 191 processes: 5 running, 186 sleeping
> >  > CPU 0: 47.1% user,  0.0% nice, 51.4% system, 0.0% interrupt,  1.6%
> >  > idle CPU 1: 38.4% user,  0.0% nice, 60.4% system,  0.0% interrupt,
> >  > 1.2% idle CPU 2: 38.8% user,  0.0% nice, 59.2% system,  0.0%
> >  > interrupt, 2.0% idle CPU 3: 45.5% user,  0.0% nice, 51.0% system,
> >  > 0.4% interrupt, 3.1% idle Mem: 677M Active, 5600M Inact, 1083M
> >  > Wired, 178M Cache, 816M Buf,301M Free
> >  > Swap: 16G Total, 1352M Used, 15G Free, 8% Inuse
> >
> > Others have covered the swap / inactive memory issue.
> >
> > But I'd expect this to be slow, for any new work anyway .. there's
> > next to no idle on any CPU.  I'd be asking, what's all of that system
> > usage?
> >
> this is building ports in the background. Still, used doing this ones a
> month, I know the feeling when the ports are updated. This one was
> really slow. Hopefully, it was just an unlucky coincidence.
>
> I rebooted meanwhile the machine. It is faster now, I would say, it is
> back to normal now. It did not come to its limits since the new start.
> It is now on:
>
> FreeBSD 10.3-STABLE #3 r314363
>
> Erich
>

Well, looks like over half of the CPU is running in system space and that
seems rather high for what I would assume is compilation. I thinnk you will
need to  poke around with things like systat, and the like to see just what
the system is doing for 55% or so of all CPUs. Since there doe snot seem to
be a lot of IO or memory at issue, the various command for those are
probably not very interesting. Probably not lock stats, either.

This reminds me of when some operation (IIRC NFS related) was calling
system time routines that are fairly expensive on FreeBSD almost
continually.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD 11.0: Installation of icingaweb2

[Kevin Oberman]

On Tue, Feb 7, 2017 at 11:19 PM, Kevin Oberman <rkober...@gmail.com> wrote:

> On Tue, Feb 7, 2017 at 5:02 PM, Kevin Oberman <rkober...@gmail.com> wrote:
>
>> On Tue, Feb 7, 2017 at 10:41 AM, Lars Engels <lars.eng...@0x20.net>
>> wrote:
>>
>>> On Mon, Feb 06, 2017 at 05:48:23PM +0100, Thorsten Baumeister wrote:
>>> > Hi folks,
>>> > last weekend I tried to install the port icingaweb2 on a patched
>>> > FreeBSD 11.0 server. 'make' worked fine, but 'make install' failed.
>>> > Has anyone seen / resolved this problem?
>>> >
>>> > ===>  Checking if icingaweb2 already installed
>>> > ===>   Registering installation for icingaweb2-2.4.1
>>> > pkg-static: Unable to access file /usr/ports/net-mgmt/icingaweb2
>>> /work/stage/usr/local/share/examples/icingaweb2/apache/icingaweb2.conf:
>>> No such file or directory
>>> > pkg-static: Unable to access file /usr/ports/net-mgmt/icingaweb2
>>> /work/stage/usr/local/share/examples/icingaweb2/nginx/icingaweb2.conf:
>>> No such file or directory
>>> > *** Error code 74
>>> >
>>> > Stop.
>>> > make[1]: stopped in /usr/ports/net-mgmt/icingaweb2
>>> > *** Error code 1
>>> >
>>> > Stop.
>>> > make: stopped in /usr/ports/net-mgmt/icingaweb2
>>> >
>>> Hi Thorsten,
>>>
>>> I am the maintainer of the icingaweb2 port.
>>> Unfortunately, I cannot reproduce this. The poudriere run doesn't show
>>> this behaviour.
>>>
>>> Do you have any local modifications?
>>>
>>>
>>> Lars
>>>
>>
>> Lars,
>>
>> The pkg-plist certainly contains 
>> "%%PORTEXAMPLESEXAMPLESDIR%%/nginx/icingaweb2.conf"
>> but I don't find that file (or any reference to nginx) in either the
>> distribution or in github. Unless some part of the build generates this
>> file (which is possible, I guess), I can't figure out where it comes from.
>> Only the apache example config is found.
>>
>> I'm not willing to install php56 right now. It will be a while before my
>> chromium rebuild is done.So I can't do any real testing on it ATM. Maybe
>> tonight or tomorrow. Then i can look through the logs and find out exactly
>> where this file does (or does not) come from and whether the package
>> installs OK for me. M.B. I don't use nginx PHP, though, so I won't be
>> testing it, just building..
>> --
>> Kevin Oberman, Part time kid herder and retired Network Engineer
>> E-mail: rkober...@gmail.com
>> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>>
>
> I did install the port and found that themising file SHOUL be te very last
> things the stage operation does.
> "(cd /usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2
> &&  ./bin/icingacli setup config webserver nginx --path=/icingaweb2
> --root=/usr/local/www/icingaweb2/public --config=/usr/local/etc/icingaweb2
> --file=/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/share/examples/
> icingaweb2/nginx/icinga\
> web2.conf)
>
> So it is generated and for some reason it was not. I have not had time to
> look at the internal make scripts to see if there are options that might
> cause the file not to be generated.
>
> Thorsten, can you provide the final lines of the "stage"operation when you
> build? The lines of interest are the four lines before "===>  Checking if
> icingaweb2 already installed"? This is where the file should be generated.
>

Should not post too late when tired. While rout lines would probably show
something, twenty is more likely to provide useful information. If you can
put up the full log somewhere, that would be even better.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD 11.0: Installation of icingaweb2

[Kevin Oberman]

On Tue, Feb 7, 2017 at 5:02 PM, Kevin Oberman <rkober...@gmail.com> wrote:

> On Tue, Feb 7, 2017 at 10:41 AM, Lars Engels <lars.eng...@0x20.net> wrote:
>
>> On Mon, Feb 06, 2017 at 05:48:23PM +0100, Thorsten Baumeister wrote:
>> > Hi folks,
>> > last weekend I tried to install the port icingaweb2 on a patched
>> > FreeBSD 11.0 server. 'make' worked fine, but 'make install' failed.
>> > Has anyone seen / resolved this problem?
>> >
>> > ===>  Checking if icingaweb2 already installed
>> > ===>   Registering installation for icingaweb2-2.4.1
>> > pkg-static: Unable to access file /usr/ports/net-mgmt/icingaweb2
>> /work/stage/usr/local/share/examples/icingaweb2/apache/icingaweb2.conf:
>> No such file or directory
>> > pkg-static: Unable to access file /usr/ports/net-mgmt/icingaweb2
>> /work/stage/usr/local/share/examples/icingaweb2/nginx/icingaweb2.conf:
>> No such file or directory
>> > *** Error code 74
>> >
>> > Stop.
>> > make[1]: stopped in /usr/ports/net-mgmt/icingaweb2
>> > *** Error code 1
>> >
>> > Stop.
>> > make: stopped in /usr/ports/net-mgmt/icingaweb2
>> >
>> Hi Thorsten,
>>
>> I am the maintainer of the icingaweb2 port.
>> Unfortunately, I cannot reproduce this. The poudriere run doesn't show
>> this behaviour.
>>
>> Do you have any local modifications?
>>
>>
>> Lars
>>
>
> Lars,
>
> The pkg-plist certainly contains 
> "%%PORTEXAMPLESEXAMPLESDIR%%/nginx/icingaweb2.conf"
> but I don't find that file (or any reference to nginx) in either the
> distribution or in github. Unless some part of the build generates this
> file (which is possible, I guess), I can't figure out where it comes from.
> Only the apache example config is found.
>
> I'm not willing to install php56 right now. It will be a while before my
> chromium rebuild is done.So I can't do any real testing on it ATM. Maybe
> tonight or tomorrow. Then i can look through the logs and find out exactly
> where this file does (or does not) come from and whether the package
> installs OK for me. M.B. I don't use nginx PHP, though, so I won't be
> testing it, just building..
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>

I did install the port and found that themising file SHOUL be te very last
things the stage operation does.
"(cd /usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2 &&
./bin/icingacli setup config webserver nginx --path=/icingaweb2
--root=/usr/local/www/icingaweb2/public --config=/usr/local/etc/icingaweb2
--file=/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/share/examples/icingaweb2/nginx/icinga\
web2.conf)

So it is generated and for some reason it was not. I have not had time to
look at the internal make scripts to see if there are options that might
cause the file not to be generated.

Thorsten, can you provide the final lines of the "stage"operation when you
build? The lines of interest are the four lines before "===>  Checking if
icingaweb2 already installed"? This is where the file should be generated.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD 11.0: Installation of icingaweb2

[Kevin Oberman]

On Tue, Feb 7, 2017 at 10:41 AM, Lars Engels <lars.eng...@0x20.net> wrote:

> On Mon, Feb 06, 2017 at 05:48:23PM +0100, Thorsten Baumeister wrote:
> > Hi folks,
> > last weekend I tried to install the port icingaweb2 on a patched
> > FreeBSD 11.0 server. 'make' worked fine, but 'make install' failed.
> > Has anyone seen / resolved this problem?
> >
> > ===>  Checking if icingaweb2 already installed
> > ===>   Registering installation for icingaweb2-2.4.1
> > pkg-static: Unable to access file /usr/ports/net-mgmt/
> icingaweb2/work/stage/usr/local/share/examples/
> icingaweb2/apache/icingaweb2.conf: No such file or directory
> > pkg-static: Unable to access file /usr/ports/net-mgmt/
> icingaweb2/work/stage/usr/local/share/examples/
> icingaweb2/nginx/icingaweb2.conf: No such file or directory
> > *** Error code 74
> >
> > Stop.
> > make[1]: stopped in /usr/ports/net-mgmt/icingaweb2
> > *** Error code 1
> >
> > Stop.
> > make: stopped in /usr/ports/net-mgmt/icingaweb2
> >
> Hi Thorsten,
>
> I am the maintainer of the icingaweb2 port.
> Unfortunately, I cannot reproduce this. The poudriere run doesn't show
> this behaviour.
>
> Do you have any local modifications?
>
>
> Lars
>

Lars,

The pkg-plist certainly contains
"%%PORTEXAMPLESEXAMPLESDIR%%/nginx/icingaweb2.conf" but I don't find
that file (or any reference to nginx) in either the distribution or in
github. Unless some part of the build generates this file (which is
possible, I guess), I can't figure out where it comes from. Only the apache
example config is found.

I'm not willing to install php56 right now. It will be a while before my
chromium rebuild is done.So I can't do any real testing on it ATM. Maybe
tonight or tomorrow. Then i can look through the logs and find out exactly
where this file does (or does not) come from and whether the package
installs OK for me. M.B. I don't use nginx PHP, though, so I won't be
testing it, just building..
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD 11.0: Installation of icingaweb2

[Kevin Oberman]

On Mon, Feb 6, 2017 at 8:48 AM, Thorsten Baumeister <
thorsten_baumeis...@gmx.de> wrote:

> Hi folks,
> last weekend I tried to install the port icingaweb2 on a patched FreeBSD
> 11.0 server. 'make' worked fine, but 'make install' failed. Has anyone seen
> / resolved this problem?
>
> Thorsten
>
> ===>  Checking if icingaweb2 already installed
> ===>   Registering installation for icingaweb2-2.4.1
> pkg-static: Unable to access file /usr/ports/net-mgmt/
> icingaweb2/work/stage/usr/local/share/example 
> s/icingaweb2/apache/icingaweb2.conf:
> No such file or directory
> pkg-static: Unable to access file /usr/ports/net-mgmt/
> icingaweb2/work/stage/usr/local/share/example
> s/icingaweb2/nginx/icingaweb2.conf: No such file or directory
> *** Error code 74
>
> Stop.
> make[1]: stopped in /usr/ports/net-mgmt/icingaweb2
> *** Error code 1
>
> Stop.
> make: stopped in /usr/ports/net-mgmt/icingaweb2
> - mobile Mail -
>

To be literal, it means that icingaweb2.conf is in the pkg-plist for the
port but was not present in the staged port installation. This is often an
error in the pkg-plist file of the port, but may be an error in the make or
the stage sections of the port build. Since this is a sample configuration
file, if you have an immediate need to get the new version installed, you
can just delete it from pkg-plist.

It does appear that the nginx directory in the distribution is not there.
Only apache. Oddly, I don't find anything in the changelog or looking at
old releases to indicate that it has existed. Looks like a quick edit to
pkg-plist will fix it up for you.

Have you reported this issue to the maintainer? ("make maintainer" will
tell you the address.)
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Building Kernel and World with -j

[Kevin Oberman]

On Mon, Jan 23, 2017 at 6:10 AM, Lowell Gilbert <
freebsd-stable-lo...@be-well.ilk.org> wrote:

> Walter Parker <walt...@gmail.com> writes:
>
> > For decades there has always been a warning not to do parallel builds of
> > the kernel or the world (Linux kernel builds also suggest not to do
> this).
> >
> > Every once in a while, I see people post about 5 minutes. This only way I
> > can see this happening is by doing a parallel build (-j 16 on a Xeon
> > Monster box).
> >
> > Are parallel builds safe? If not, what are actual risk factors and can
> they
> > be mitigated?
>
> As a general rule, it's safe. But don't report failures from a
> parallel build.
>
> This is not so much an issue of parallel builds being unsupported
> as of the logs being harder to read.


Use of parallel builds of world and kernel are and have been supported
since at least 10.0. If a parallel build fails, the first step is usually
to do a single-job build. If it succeeds, there is a bug in the make
scripts that should be reported. If the single-job build also fails, a bug
should be reported with any errors included from the non-parallel build as
the parallel build makes the error context very difficult or even
impossible to determine from the log.

Generally, I think the number of jobs should be slightly greater than the
number of available CPU threads. Back in 10.0 days I ran some tests that
showed the for 4 and 8 thread systems the improvements for large numbers of
jobs peaked at about CPU thread count + 2 and significantly larger numbers
of jobs caused a slight deterioration in performance. This was not true on
early hyper-threaded CPUs which did not effectively optimize
hyper-threading and things may have changed in the 6 or 7 years since I
tested and may be very different for systems with large numbers of threads
seen in servers today.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 10.3-RELEASE-p13 "unsupported file layout"

[Kevin Oberman]

On Wed, Jan 11, 2017 at 8:24 PM, George Mitchell <george+free...@m5p.com>
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 of a custom kernel is
> >> incorrect. This is a common misconception and, in cases of very limited
> >> disk space, may be true, it is rare. It is helped by the fact that the
> man
> >> page makes no mention of how to so this. (You do still need to build a
> new
> >> kernel if the update does, indeed, touch the kernel.)
> >>
> >> All you need is a GENERIC kernel in /boot/GENERIC. You can either build
> it
> >> or download it. See the FreeBSD Handbook Section 23.2.3.1, “Custom
> Kernels
> >> with FreeBSD 9.X and Later”
> >> <https://www.freebsd.org/doc/en_US.ISO8859-1/books/
> handbook/updating-upgrading-freebsdupdate.html#freebsd-
> update-custom-kernel-9x>
> >> for details on downloading a GENERIC kernel. Before any upgrade, major
> or
> >> minor, you might wat to re-reas that section.
> >>
> >> Once the GENERIC kernel is in /boot, you may use freebsd-update and, if
> the
> >> GENERIC kernel is not updated, you're good to go. If it is, you will
> need
> >> to build and install a new custom kernel and reboot. Since most security
> >> patches don't touch the kernel, this is usually not needed. I believe
> that
> >> the 10.3 kernel was last touched in p11.
> >> --
> >> Kevin Oberman, Part time kid herder and retired Network Engineer
> >> E-mail: rkober...@gmail.com
> >> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
> >> ___
> >> freebsd-stable@freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@
> freebsd.org"
> >>
> > Thanks, I'll try that the next time I have a chance.  When I naively
> > tried a straight "freebsd-update" a few months ago, of course it
> > overwrote my SCHED_4BSD kernel with a SCHED_ULE one.-- George
> >
> Just to refresh my memory of what happened a few months ago, I tried
> the following experiment.  I copied my current modified kernel:
>
> rsync -av /boot/kernel/ /boot/my.kernel/
>
> Then with my modified kernel still in place, I said:
>
> freebsd-update fetch
> freebsd-update install
>
> With not a qualm in the world, freebsd-update installed a fresh
> SCHED_ULE kernel in /boot.  (Happily, it did save my current kernel
> in /boot/kernel.old.)  That's what happened last year, too.  Why
> didn't freebsd-update notice that I had a modified kernel and at
> least notify me that something funky was going on?  -- George


I'm a bit surprised that there was no message about the kernel being
non-GENERIC, but I've never tried. The key is the presence of
/boot/GENERIC. If it is present, the kernel in /boot/kernel is left
untouched and /boot/GENERIC is updated to the new version. If /boot/GENERIC
does not exist, then the update is performed on /boot/kernel/kernel. (N.B.
Kernel modules are always updated when or if needed!)
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 10.3-RELEASE-p13 "unsupported file layout"

[Kevin Oberman]

On Wed, Jan 11, 2017 at 12:24 PM, George Mitchell <george+free...@m5p.com>
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 layout
> *** Error code 1
>
> Stop.
> make[4]: stopped in /usr/src/lib/libc
> *** Error code 1
>
> Stop.
> make[3]: stopped in /usr/src
> *** Error code 1
>
> Stop.
> make[2]: stopped in /usr/src
> *** Error code 1
>
> Stop.
> make[1]: stopped in /usr/src
> *** Error code 1
>
> Stop.
> make: stopped in /usr/src
>
> freebsd-version -ku
> 10.3-RELEASE-p13
> 10.3-RELEASE-p15
>
> I am using a generic kernel, except for using SCHED_4BSD.  If it
> weren't for that, I would just use freebsd-update.
>
> Googling suggests that my build tree is somehow mixing up 32 and 64
> bit files.  (I'm running on an amd64 machine.)  How do I get this
> cleared up? -- George
>

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 true, it is rare. It is helped by the fact that the man
page makes no mention of how to so this. (You do still need to build a new
kernel if the update does, indeed, touch the kernel.)

All you need is a GENERIC kernel in /boot/GENERIC. You can either build it
or download it. See the FreeBSD Handbook Section 23.2.3.1, “Custom Kernels
with FreeBSD 9.X and Later”
<https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html#freebsd-update-custom-kernel-9x>
for details on downloading a GENERIC kernel. Before any upgrade, major or
minor, you might wat to re-reas that section.

Once the GENERIC kernel is in /boot, you may use freebsd-update and, if the
GENERIC kernel is not updated, you're good to go. If it is, you will need
to build and install a new custom kernel and reboot. Since most security
patches don't touch the kernel, this is usually not needed. I believe that
the 10.3 kernel was last touched in p11.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: make buildkernel does not respect KERNCONF or JOBS in /etc/make.conf

[Kevin Oberman]

On Mon, Dec 12, 2016 at 4:20 PM, Herbert J. Skuhra <herb...@mailbox.org>
wrote:

> Kevin Oberman skrev:
> >
> > Clearly the documentation is a bit behind the times. For some time people
> > have used KERNCONF to build multiple kernels, but that was a lucky things
> > that was not officially supported. It just happened to work. Then, with
> > 11.0, it no longer did in many cases sue to changes in the kernel build
> > system. When people complained, there did not seem to be a way to fix
> this
> > without blocking future goals in speeding up and enhancinghte standard
> > kernel build.
> >
> > The result was BUILDKERNELS. It was specifically designed to allow the
> > building of multiple kernels and the appropriate modules. This would
> always
> > take longer and use more disk space, but it would work reliably. Now, bit
> > building a single, local kernel, KERNCONF is the best way, though I
> suspect
> > that it make only a small difference until new capabilities are added
> later
> > in the life of 11.
> >
> > So, while it seems the man pages need to catch up, building multiple
> > kernels should be done with KERNCONF in either make.conf or src.conf and
> > multiple kernels with BUILDKERNELS.
> >
> > This is from my recollection of the discussion thread. I'll admit to
> being
> > too lazy to go find and read all of it. I suspect it was on current@,
> but
> > I'm not even sure of that.
>
> ???
>
> From /usr/src/Makefile.inc1:
>
>1137 .if ${TARGET_ARCH} == "powerpc64"
>1138 KERNCONF?=  GENERIC64
>1139 .else
>1140 KERNCONF?=  GENERIC
>1141 .endif
>[...]
>1149 BUILDKERNELS=
>1150 INSTALLKERNEL=
>1151 .if defined(NO_INSTALLKERNEL)
>1152 # All of the BUILDKERNELS loops start at index 1.
>1153 BUILDKERNELS+= dummy
>1154 .endif
>1155 .for _kernel in ${KERNCONF}
>1156 .if exists(${KERNCONFDIR}/${_kernel})
>1157 BUILDKERNELS+=  ${_kernel}
>1158 .if empty(INSTALLKERNEL) && !defined(NO_INSTALLKERNEL)
>1159 INSTALLKERNEL= ${_kernel}
>1160 .endif
>1161 .endif
>1162 .endfor
>
> So setting BUILDKERNELS has no effect.
>
> --
> Herbert
>

I think you miss the significance. BUILDKERNELS only is used to build the
kernels. It is not used by installkernel as installing two kernels does not
make sense. It is ONLY used to build multiple kernels. KERNCONF is still
used to specify the kernel, with attendant modules, to be installed.

I should also mention that, if you want to install a new kernel without
overwriting the old kernel and modules (/boot/kernel.old/), "make
reinstallkernel". It replaces the existing kernel instead of renaming the
kernel directory to kernel.old. I find this very handy, but it is poorly
documented. So, if you want to install GENERIC and not lose your last
working kernel, "make reinstallkernel KERNCONF=GENERIC". That will blow
away the bad kernel and modules and install GENERIC. Note that it does not
touch the /usr/obj directory that PUMPKIN is built in, so PUMPKIN and
similarly be reinstalled.

The man page for src.conf is automatically generated and only lists those
values which are specific to src.conf (WITH_ and WITHOUT_) and describes
its use. It is used as input for system builds and installs but should not
be accessed for any other purpose. make.conf is always read by make with no
regard to what is being made. (N.B. I believe that some people have ignored
this in some ports stuff.) Anything that is put into make.conf may be
placed in src,conf if you only want to have it used when
building/installing the kernel and world.

I'm probably forgetting something, but I hope this explains it a bit.
--
Kevin Oberman, Retired Network Engineer and kid herder
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: make buildkernel does not respect KERNCONF or JOBS in /etc/make.conf

[Kevin Oberman]

On Mon, Dec 12, 2016 at 1:16 AM, tech-lists <tech-li...@zyxst.net> wrote:

> On 12/12/2016 09:07, Thomas Mueller wrote:
>
>> My question is, do you build modules redundantly, or just once?
>> I don't want to build the same modules more than once.
>>
>
> For me - redundantly, I guess. It's not like it takes a lot of time or
> space on the compiling machine, and I ensure that everything that needs to
> be built, is built.
>
> PUMPKIN = heavily modified config with all the stuff I don't need stripped
> out, and a couple of non-default lines.
>
> GENERIC = unmodified kernel that should work if by some chance PUMPKIN
> doesn't.
> --
> J.


Clearly the documentation is a bit behind the times. For some time people
have used KERNCONF to build multiple kernels, but that was a lucky things
that was not officially supported. It just happened to work. Then, with
11.0, it no longer did in many cases sue to changes in the kernel build
system. When people complained, there did not seem to be a way to fix this
without blocking future goals in speeding up and enhancinghte standard
kernel build.

The result was BUILDKERNELS. It was specifically designed to allow the
building of multiple kernels and the appropriate modules. This would always
take longer and use more disk space, but it would work reliably. Now, bit
building a single, local kernel, KERNCONF is the best way, though I suspect
that it make only a small difference until new capabilities are added later
in the life of 11.

So, while it seems the man pages need to catch up, building multiple
kernels should be done with KERNCONF in either make.conf or src.conf and
multiple kernels with BUILDKERNELS.

This is from my recollection of the discussion thread. I'll admit to being
too lazy to go find and read all of it. I suspect it was on current@, but
I'm not even sure of that.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problems with Dell external USB DVD drive

[Kevin Oberman]

On Sun, Nov 13, 2016 at 5:56 PM, Felix Johnson <felix.the@gmail.com>
wrote:

> Hello,
>
> I have a Dell Inspiron 7547, which lacks an internal CD/DVD drive.
> I purchased a Dell DW514 external USB DVD drive, which works in Windows,
> but can't be located in FreeBSD 11.0-p2. I am looking for help in getting
> FreeBSD
> to recognize the device.
>
> Any help is appreciated, since this is an important step to using this
> laptop
> full-time as a FreeBSD workstation.
>
> Here is the information I have on my system:
>
> [fjohnson@laptop /usr/home/fjohnson]$ uname -a
> FreeBSD laptop 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24
> 06:55:27 UTC 2016
> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
>  amd64
>
> [fjohnson@laptop /usr/home/fjohnson]$ sudo usbconfig
> ugen0.1:  at usbus0, cfg=0 md=HOST spd=SUPER
> (5.0Gbps) pwr=SAVE (0mA)
> ugen1.1:  at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps)
> pwr=SAVE (0mA)
> ugen0.2:  at usbus0, cfg=0 md=HOST spd=HIGH
> (480Mbps) pwr=SAVE (100mA)
> ugen1.2:  at usbus1, cfg=0 md=HOST spd=HIGH
> (480Mbps) pwr=SAVE (0mA)
> ugen0.3:  at usbus0, cfg=0 md=HOST spd=FULL (12Mbps)
> pwr=ON (98mA)
> ugen0.4:  at usbus0, cfg=0 md=HOST spd=HIGH
> (480Mbps) pwr=ON (450mA)
> ugen0.5:  at usbus0, cfg=0 md=HOST spd=HIGH
> (480Mbps) pwr=ON (500mA)
> ugen0.6:  at usbus0, cfg=0 md=HOST spd=HIGH
> (480Mbps) pwr=ON (500mA)
> ugen0.7:  at usbus0, cfg=0 md=HOST spd=FULL (12Mbps)
> pwr=ON (100mA)
>
> [...]
>


> Thank you!
> Felix Johnson
>

Can I assume that the drive was plugged in when the usbconfig command was
issued? I don't see any indication of it in the output. I was expecting a
vendor/product that was not known to the system, but that does nto appear
to be the case. the only two not identified have and the first in an Intel
vendor ID and the second appears to be an Asix Ethernet controller, though
the information on that is sketchy.

When you plug in the drive, the console should show a message. A similar
message should be sent when it is unplugged. Can you try that and report
the message? It should include the vendor and product IDs.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: ath0 associated, wlan0 not associated

[Kevin Oberman]

On Sat, Nov 5, 2016 at 11:58 AM, George Mitchell <george+free...@m5p.com>
wrote:

> On 11/05/16 13:00, George Mitchell wrote:
> > On 11/05/16 01:05, Adrian Chadd wrote:
> >> nope, sorry.  There's a lot of work in the -11 wifi stack and drivers.
> >>
> >>
> >> -a
> >>
> >> [...]
> >
> > Okay, I downloaded and installed 11.0-RELEASE on a spare slice, and
> > dmesg tells me the following (with regard to ath0):
> >
> >
> > ath0:  mem 0xf0a0-0xf0a7 irq 36 at
> > device 0.0 on pci2
> > ath0: WB335 2-ANT card detected
> > ath0: Bluetooth Antenna Diversity card detected
> > ath0: [HT] enabling HT modes
> > ath0: [HT] enabling short-GI in 20MHz mode
> > ath0: [HT] 1 stream STBC receive enabled
> > ath0: [HT] 1 RX streams; 1 TX streams
> > ath0: QCA9565 mac 704.1 RF5110 phy 2523.1
> > ath0: 2GHz radio: 0x; 5GHz radio: 0x
> >
> > But ifconfig tells me there is no "ath0" interface ... Does 11.0
> > handle wifi in some unfamiliar manner?  I put my usual wifi magic
> > into rc.conf:
> >
> > create_args_wlan0="country US"
> > ifconfig_wlan0="WPA DHCP"
> > wlans_ath0="wlan0"
> >
> > -- George
> >
> I forgot to copy my wpa_supplicant.conf over.  Now it works!  (I
> guess the invisible ath0 is just how 11.0 works?)  -- George


Yes, as you speculate, the 802.11 software had a major rework and only the
wlan interface is visible. It is due to this re-work that the changes to
the wireless drivers can't be reasonably back-ported to 10.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: huge nanosleep variance on 11-stable

[Kevin Oberman]

On Tue, Nov 1, 2016 at 10:16 PM, Jason Harmening <jason.harmen...@gmail.com>
wrote:

>
>
> On 11/01/16 20:45, Kevin Oberman wrote:
> > On Tue, Nov 1, 2016 at 2:36 PM, Jason Harmening
> > <jason.harmen...@gmail.com <mailto:jason.harmen...@gmail.com>> wrote:
> >
> > Sorry, that should be ~*30ms* to get 30fps, though the variance is
> still
> > up to 500ms for me either way.
> >
> > On 11/01/16 14:29, Jason Harmening wrote:
> > > repro code is at http://pastebin.com/B68N4AFY if anyone's
> interested.
> > >
> > > On 11/01/16 13:58, Jason Harmening wrote:
> > >> Hi everyone,
> > >>
> > >> I recently upgraded my main amd64 server from 10.3-stable
> > (r302011) to
> > >> 11.0-stable (r308099).  It went smoothly except for one big issue:
> > >> certain applications (but not the system as a whole) respond very
> > >> sluggishly, and video playback of any kind is extremely choppy.
> > >>
> > >> The system is under very light load, and I see no evidence of
> > abnormal
> > >> interrupt latency or interrupt load.  More interestingly, if I
> > place the
> > >> system under full load (~0.0% idle) the problem *disappears* and
> > >> playback/responsiveness are smooth and quick.
> > >>
> > >> Running ktrace on some of the affected apps points me at the
> problem:
> > >> huge variance in the amount of time spent in the nanosleep system
> > call.
> > >> A sleep of, say, 5ms might take anywhere from 5ms to ~500ms from
> > entry
> > >> to return of the syscall.  OTOH, anything CPU-bound or that waits
> on
> > >> condvars or I/O interrupts seems to work fine, so this doesn't
> > seem to
> > >> be an issue with overall system latency.
> > >>
> > >> I can repro this with a simple program that just does a 3ms
> > usleep in a
> > >> tight loop (i.e. roughly the amount of time a video player would
> > sleep
> > >> between frames @ 30fps).  At light load ktrace will show the huge
> > >> nanosleep variance; under heavy load every nanosleep will
> complete in
> > >> almost exactly 3ms.
> > >>
> > >> FWIW, I don't see this on -current, although right now all my
> > -current
> > >> images are VMs on different HW so that might not mean anything.
> > I'm not
> > >> aware of any recent timer- or scheduler- specific changes, so I'm
> > >> wondering if perhaps the recent IPI or taskqueue changes might be
> > >> somehow to blame.
> > >>
> > >> I'm not especially familiar w/ the relevant parts of the kernel,
> > so any
> > >> guidance on where I should focus my debugging efforts would be
> much
> > >> appreciated.
> > >>
> > >> Thanks,
> > >> Jason
> >
> >
> > This is likely off track, but this is a behavior I have noticed since
> > moving to 11, though it might have started in 10.3-STABLE before moving
> > to head before 11 went to beta. I can't explain any way nanosleep could
> > be involved, but I saw annoying lock-ups similar to yours. I also no
> > longer see them.
> >
> > I eliminated the annoyance by change scheduler from ULE to 4BSD. That
> > was it, but I have not seen the issue since. I'd be very interested in
> > whether the scheduler is somehow impacting timing functions or it's s
> > different issue. I've felt that there was something off in ULE for some
> > time, but it was not until these annoying hiccups convinced me to try
> > going back to 4BSD.
> >
> > Tip o' the hat to Doug B. for his suggestions that ULE may have issues
> > that impacted interactivity.
>
> I figured it out: r282678 (which was never MFCed to 10-stable) added
> support for the MWAIT instruction on the idle path for Intel CPUs that
> claim to support it.
>
> While my CPU (2009-era Xeon 5500) advertises support for it in its
> feature mask and ACPI C-state entries, the cores don't seem to respond
> very quickly to interrupts while idling in MWAIT.  Disabling mwait in
> acpi_cpu.c and falling back to the old "sti; hlt" mechanism for C1
> completely fixes the responsiveness issues.
>
> So if your CPU is of a similar vintage, it may not be ULE's fault.
>
>
You are almost certain

Re: huge nanosleep variance on 11-stable

[Kevin Oberman]

On Tue, Nov 1, 2016 at 2:36 PM, Jason Harmening 
wrote:

> Sorry, that should be ~*30ms* to get 30fps, though the variance is still
> up to 500ms for me either way.
>
> On 11/01/16 14:29, Jason Harmening wrote:
> > repro code is at http://pastebin.com/B68N4AFY if anyone's interested.
> >
> > On 11/01/16 13:58, Jason Harmening wrote:
> >> Hi everyone,
> >>
> >> I recently upgraded my main amd64 server from 10.3-stable (r302011) to
> >> 11.0-stable (r308099).  It went smoothly except for one big issue:
> >> certain applications (but not the system as a whole) respond very
> >> sluggishly, and video playback of any kind is extremely choppy.
> >>
> >> The system is under very light load, and I see no evidence of abnormal
> >> interrupt latency or interrupt load.  More interestingly, if I place the
> >> system under full load (~0.0% idle) the problem *disappears* and
> >> playback/responsiveness are smooth and quick.
> >>
> >> Running ktrace on some of the affected apps points me at the problem:
> >> huge variance in the amount of time spent in the nanosleep system call.
> >> A sleep of, say, 5ms might take anywhere from 5ms to ~500ms from entry
> >> to return of the syscall.  OTOH, anything CPU-bound or that waits on
> >> condvars or I/O interrupts seems to work fine, so this doesn't seem to
> >> be an issue with overall system latency.
> >>
> >> I can repro this with a simple program that just does a 3ms usleep in a
> >> tight loop (i.e. roughly the amount of time a video player would sleep
> >> between frames @ 30fps).  At light load ktrace will show the huge
> >> nanosleep variance; under heavy load every nanosleep will complete in
> >> almost exactly 3ms.
> >>
> >> FWIW, I don't see this on -current, although right now all my -current
> >> images are VMs on different HW so that might not mean anything.  I'm not
> >> aware of any recent timer- or scheduler- specific changes, so I'm
> >> wondering if perhaps the recent IPI or taskqueue changes might be
> >> somehow to blame.
> >>
> >> I'm not especially familiar w/ the relevant parts of the kernel, so any
> >> guidance on where I should focus my debugging efforts would be much
> >> appreciated.
> >>
> >> Thanks,
> >> Jason
>

This is likely off track, but this is a behavior I have noticed since
moving to 11, though it might have started in 10.3-STABLE before moving to
head before 11 went to beta. I can't explain any way nanosleep could be
involved, but I saw annoying lock-ups similar to yours. I also no longer
see them.

I eliminated the annoyance by change scheduler from ULE to 4BSD. That was
it, but I have not seen the issue since. I'd be very interested in whether
the scheduler is somehow impacting timing functions or it's s different
issue. I've felt that there was something off in ULE for some time, but it
was not until these annoying hiccups convinced me to try going back to
4BSD.

Tip o' the hat to Doug B. for his suggestions that ULE may have issues that
impacted interactivity.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: I'm upset about FreeBSD

[Kevin Oberman]

On Wed, Oct 19, 2016 at 3:39 PM, Warner Losh <i...@bsdimp.com> wrote:

> On Wed, Oct 19, 2016 at 12:21 PM, Rostislav Krasny <rosti@gmail.com>
> wrote:
> > On Tue, Oct 18, 2016 at 21:57:29 +1100, Ian Smith <smi...@nimnet.asn.au>
> wrote:
> >>
> >> If FreeBSD GPT images (and Kindle readers) can trigger this, so could a
> >> theoretically unlimited combination of data on block 2 of USB media;
> >> modifying FreeBSD to fix a Windows bug should be out of the question.
> >
> > Not modifying FreeBSD and not fixing Windows bug but modifying the
> > FreeBSD installation media and working around the Windows bug to let
> > people install FreeBSD without disappointing at very beginning. Why
> > GPT is used in the memstick images at all? Why they can't be MBR
> > based? I think they can.
>
> Can't boot UEFI off of MBR disks on all BIOSes.
>
> Warner
>

I'll go one farther. You can't boot many new PCs with traditional MBR
disks. And. please don't  confuse GPT with UEFI. I have yet to find an
amd64 computer that has a problem with a GPT format with MBR. Due to broken
BIOS, my 5-year old ThinkPad won't boot UEFI, but it has no problem with
MBR, whether GPT formatted or not. As far as I know, the 11.0 memstick
images are still MBR, just on a GPT structured disk, not UEFI. (Let me know
if I am mistaken on this.)

I do accept that some early amd64 systems and, perhaps, many i386 systems
may have problems with GPT, but GPT was designed to be compatible with
traditional disk formats and, while they may have problems, they really
should work for single partition disks. And I understand that it is
frustrating if you hit one of these cases where it fails.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: make buildwotrld can not find zlib,h

[Kevin Oberman]

On Tue, Oct 18, 2016 at 12:10 AM, Schaich Alonso <alonsoscha...@fastmail.fm>
wrote:

> On Fri, 14 Oct 2016 11:06:55 -0700
> Kevin Oberman <rkober...@gmail.com> wrote:
>
> > On Fri, Oct 14, 2016 at 6:10 AM, Dmitry Luhtionov <
> dmitryluhtio...@gmail.com
> > > wrote:
> >
> > > c++  -O2 -pipe
> > > -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include
> > > -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/
> > > include
> > > -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support
> -I.
> > > -I/usr/src/lib/clang/libllvmsupport/../../../
> contrib/llvm/../../lib/clang/
> > > include
> > > -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS
> > > -D__STDC_CONSTANT_MACROS -DNDEBUG -fno-strict-aliasing
> > > -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd11.0\"
> > > -DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd11.0\"
> > > -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/tmp\" -MD
> -MF.depend.Compression.o
> > > -MTCompression.o -Qunused-arguments
> > > -I/usr/obj/usr/src/tmp/legacy/usr/include  -std=c++11 -fno-exceptions
> > > -fno-rtti -stdlib=libc++ -Wno-c++11-extensions  -c
> > > /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/
> > > Compression.cpp
> > > -o Compression.o
> > > /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/
> > > Compression.cpp:21:10:
> > > fatal error: 'zlib.h' file not found
> > > #include 
> > >  ^
> > > 1 error generated.
> > >
> >
> > Very odd. /usr/include/zlib.h is and long has been a standard component
> of
> > FreeBSD and should be present on your system. Can you confirm its
> absence?
> > Anything that could be in /etc/src.conf that might trigger this? (I can't
> > see anything obvious, but src.conf(5) is very long.)
> >
> > I'm also not sure whether, at this point in the build, you should be
> using
> > the system's include files or those in /usr/obj/usr/src/tmp/usr/include/
> or
> > /usr/src/lib/libz/zlib.h, which is what should be copied to
> > /usr/obj/usr/src/tmp/usr/include. Normally the system's files are not
> used
> > during the build.
> >
> > Have you tried completely removing /usr/obj (rm -r /usr/obj/*) before
> > starting the build with -DNO_CLEAN?
> > --
> > Kevin Oberman, Part time kid herder and retired Network Engineer
> > E-mail: rkober...@gmail.com
> > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>
>
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>
> Hi,
>
> I'm having an issue with libarchive that might or might not be related:
>
> > [...]
> > (cd /usr/src/lib/libarchive/tests &&  DEPENDFILE=.depend.libarchive_test
> NO_SUBDIR=1 make -f /usr/src/lib/libarchive/tests/Makefile
> _RECURSING_PROGS=t  PROG=libarchive_test )
> > cc -O2 -pipe -I/usr/src/lib/libarchive 
> > -I/usr/obj/usr/src/lib/libarchive/tests
> -I/usr/src/contrib/libarchive/libarchive 
> -I/usr/src/contrib/libarchive/test_utils
> -DHAVE_LIBLZMA=1 -DHAVE_LZMA_H=1   -g -MD  -MF.depend.libarchive_test.main.o
> -MTmain.o -std=gnu99 -fstack-protector-strong-Qunused-arguments  -c
> /usr/src/contrib/libarchive/libarchive/test/main.c -o main.o
> > /usr/src/contrib/libarchive/libarchive/test/main.c:2400:10: fatal
> error: 'list.h' file not found
> > #include "list.h"
> >  ^
> > 1 error generated.
> > *** Error code 1
> >
> > Stop.
> > make[1]: stopped in /usr/src/lib/libarchive/tests
> > *** Error code 1
> > [...]
>
> list.h is perfectly there, but it's in /usr/src/lib/libarchive/tests
> rather than /usr/obj/usr/src/lib/libarchive/tests (the second -I is
> wrong), so either some copy-to-builddir target was skipped or the build
> process should include the source path instead of the build path.
>
> I removed anything from /usr/obj/ and also commented-away anything I had
> in make.conf and src.conf prior to attempting to compile it (11-STABLE
> r307550).
>
> Alonso
>

You need to look at the output. One pass of the install should copy the new
.h files from /usr/src to /usr/obj/usr/src. Looks like one or more things
did not get copied.

Do you have an /etc/src.conf file? Are any parts of the system being
excluded there? What about /etc/make.conf? Since others have not reported
this, it seems likely that there is something you have configured at some
time.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: sshd whines & dies after releng/10 "freebsd-update" run

[Kevin Oberman]

On Sun, Oct 16, 2016 at 10:45 AM, David Wolfskill <da...@catwhisker.org>
wrote:

> On Sun, Oct 16, 2016 at 10:29:00AM -0700, Xin Li wrote:
> > ...
> > On 10/16/16 09:26, David Wolfskill wrote:
> > > And over the last year or so, it's worked pretty well:  I have the
> > > machine set up (as is usually my approach) to be able to boot from
> > > either of a couple of slices.  I use a "dump | restore" pipeline
> > > to copy the / and /usr file systems from the "active" slice to the
> > > "inactive" slice, adjust /etc/fstab on the inactive slice to reflect
> > > reality for when it's the boot slice, then (while the file systemms
> > > from the other slice are still mounted -- e.g., on /S2) run
> > > "freebsd-update -b /S2 fetch install", then reboot from the
> > > newly-updated slice.
> > >
> > > In the past, that's Just Worked.
> >
> > Your usage probably worked because you were lucky for a few times in the
> > past.  (details below)
> >
> > > This weekend, though, I was planning to update my other systems tfrom
> > > stable/10 to stable/11, so I figured I'd try freebsd-update on this
> > > machine first.
> > >
> > [...]
> > > root@sisboombah:/tmp # `which sshd` -d
> > > Undefined symbol "ssh_compat13" referenced from COPY relocation in
> /usr/sbin/sshd
> > >
> > > Any clues?
> >
> > I think this is not going to work (stable/10 -> releng/10.3) due to ABI
> > incompatibility in a downgrade.
>
> I seem to have failed to commnunicate clearly:  The machine in question
> does not, and has not, run "stable".  It runs releng.
>
> At the moment (on the "old" slice), it reports:
>
> sisboombah(10.3-RELEASE-p7)[1] uname -a
> FreeBSD sisboombah.catwhisker.org 10.3-RELEASE-p7 FreeBSD 10.3-RELEASE-p7
> #0: Thu Aug 11 18:38:15 UTC 2016 r...@amd64-builder.daemonology.net:
> /usr/obj/usr/src/sys/GENERIC  amd64
> sisboombah(10.3-RELEASE-p7)[2]
>
> > Basically, freebsd-update is treating your stable/10 as a 10.3-RELEASE
> > installation and will fetch only changes from 10.3-RELEASE to the latest
> > patchlevel.
>
> I can see that... if the machine were running stable.
>
> > Because of a SSH vulnerability that affects 10.3, freebsd-update would
> > patch libssh (shared library used by sshd and friends), however the
> > change does not affect the main binary.  This worked by replacing your
> > existing libssh with the one shipped by freebsd-update (effectively
> > downgraded the library) and that would break sshd.
>
> As a reality check:
> sisboombah(10.3-RELEASE-p7)[4] sudo mount /S2
> Password:
> sisboombah(10.3-RELEASE-p7)[5] sudo mount /S2/usr
> sisboombah(10.3-RELEASE-p7)[6] ls -lT {,/S2}/usr/lib/private/libssh.so.*
> -r--r--r--  1 root  wheel  634232 Oct 16 11:57:32 2016
> /S2/usr/lib/private/libssh.so.5
> -r--r--r--  1 root  wheel  569864 Jun  5 13:37:52 2016
> /usr/lib/private/libssh.so.5
> sisboombah(10.3-RELEASE-p7)[7] ls -lT {,/S2}/usr/sbin/ssh*
> -r-xr-xr-x  1 root  wheel  297736 Jun  5 13:38:35 2016 /S2/usr/sbin/sshd
> -r-xr-xr-x  1 root  wheel  297736 Jun  5 13:38:35 2016 /usr/sbin/sshd
> sisboombah(10.3-RELEASE-p7)[8]
>
> > I think upgrade -r 10.2-RELEASE (ideally, 11.0-RELEASE though as it
> > would eliminate the possibility of any potential incompatibility) would
> > work because that would result in a full rewrite of all files.
>
> Well, I had seen reports of folks having "issues" with attempts to
> use freebsd-update to get to releng/11 from systems that weren't
> as up-to-date as they might be; I was actually trying to avoid a
> problem :-}
>
> Peace,
> david
> --
> David H. Wolfskill  da...@catwhisker.org
> Those who would murder in the name of God or prophet are blasphemous
> cowards.
>
> See http://www.catwhisker.org/~david/publickey.gpg for my public key.
>

I believe sshd no longer supports ssh1 compatibility and it looks like you
might still have an entry in /etc/sshd/sshd.config trying to touch v1.
Check the file for any non-default entries. Compare your sshd_config with
the default version in /usr/src/crypto/openssh.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: make buildwotrld can not find zlib,h

[Kevin Oberman]

On Fri, Oct 14, 2016 at 6:10 AM, Dmitry Luhtionov <dmitryluhtio...@gmail.com
> wrote:

> c++  -O2 -pipe
> -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include
> -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/
> include
> -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I.
> -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/
> include
> -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS
> -D__STDC_CONSTANT_MACROS -DNDEBUG -fno-strict-aliasing
> -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd11.0\"
> -DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd11.0\"
> -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/tmp\" -MD -MF.depend.Compression.o
> -MTCompression.o -Qunused-arguments
> -I/usr/obj/usr/src/tmp/legacy/usr/include  -std=c++11 -fno-exceptions
> -fno-rtti -stdlib=libc++ -Wno-c++11-extensions  -c
> /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/
> Compression.cpp
> -o Compression.o
> /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/
> Compression.cpp:21:10:
> fatal error: 'zlib.h' file not found
> #include 
>  ^
> 1 error generated.
>

Very odd. /usr/include/zlib.h is and long has been a standard component of
FreeBSD and should be present on your system. Can you confirm its absence?
Anything that could be in /etc/src.conf that might trigger this? (I can't
see anything obvious, but src.conf(5) is very long.)

I'm also not sure whether, at this point in the build, you should be using
the system's include files or those in /usr/obj/usr/src/tmp/usr/include/ or
/usr/src/lib/libz/zlib.h, which is what should be copied to
/usr/obj/usr/src/tmp/usr/include. Normally the system's files are not used
during the build.

Have you tried completely removing /usr/obj (rm -r /usr/obj/*) before
starting the build with -DNO_CLEAN?
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11-current becoming 11-stable

[Kevin Oberman]

On Mon, Oct 10, 2016 at 3:48 AM, tech-lists <tech-li...@zyxst.net> wrote:

> Hi,
>
> I have a desktop that has run 11-current for at least the last year. I
> periodically rebuild kernel and world to keep on top of things. As it's a
> desktop, there are lots of ports installed. These are installed via the
> older cd /port && make install clean way, rather than poudiere.
>
> Basically I'm asking that, when 11-stable becomes available (as far as I
> can see, it's still at PRERELEASE), is it worthwhile/advisable to recompile
> all my ports after doing the make world & make delete-old dance?
>
> thanks,
> --
> J.
>

11.0-RELEASE should be showing up any day. It is on Release Candidate 3.

First, there is nothing outdated about building ports from source. The only
time using poudiere makes real sense is when you need to build a "standard"
set of ports for redistribution to other systems. If you are building for a
single system, it really is just an added complication.

The real choice is between building from ports or installing packages. If
you need to build some ports with non-standard  options, then using
packages may not work for you. Mixing ports and packages can greatly
complicate things and may result in unexpected issues, though it can work
if you are careful. For my server I use all packages EXCEPT postfix. Since
nothing depends on it, I am comfortable in building it from source whenever
it is updated. That saves me a LOT of time.

As to the need to update, most ports don't require rebuilding after the
move to 11. FreeBSD libraries use symbol versioning so that ABI should
never be broken when new versions change the API. The exception would be
contributed code that is does not have symbol versioning. The most
significant of these is probably OpenSSL. It is likely that ports that use
the base system library will fail to run on 11. If they use the port
version of OpenSSL or LibreSSL, this is not an issue. I strongly recommend
that you  install security/openssl and never link ports with the base
system libraries. If you have done this, it is likely that any ports will
need a rebuild.

There are several other contributed libraries that are not commonly used by
ports. These may cause some issues, but in general you can move from 10 to
11 and not re-build ports. You certainly won't need to re-build many.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: buildworld errors at outset on fresh svn checkout

[Kevin Oberman]

On Thu, Oct 6, 2016 at 10:16 PM, Scott Bennett <benn...@sdf.org> wrote:

>  I'm running into a problem in updating my 10-STABLE system from
> source.
> A "make buildworld" quits immediately.  I tried a fresh svn checkout for
> base/stable/10 and then tried to run buildworld again, but got the same
> error.
> I've been scratching my head over this for hours, but must be missing
> something
> simple.
>  I have ccache installed and have been using it for a fairly long time
> now.
> My /etc/src.conf contains just two lines:
>
> PORTS_MODULES=multimedia/cuse4bsd-kmod sysutils/pefs-kmod #
> emulators/virtualbox-ose-kmod
> WITH_LLDB=yes
>
> My /etc/make.conf is rather longer, so I'll append it following .sig below.
>
>  Here's what happens.
>
> Script started on Thu Oct  6 23:31:47 2016
> hellas# cd /usr/src
> hellas# nice make buildworld
> Unknown modifier '['
>
> "/usr/src/Makefile.inc1", line 1113: Malformed conditional
> (${BUILDKERNELS:[)
> Unknown modifier '['
>
> "/usr/src/Makefile.inc1", line 1122: if-less endif
> Unknown modifier '['
>
> "/usr/src/Makefile.inc1", line 1144: Malformed conditional
> (${BUILDKERNELS:[)
> Unknown modifier '['
>
> "/usr/src/Makefile.inc1", line 1161: if-less endif
> Unknown modifier '['
>
> "/usr/src/Makefile.inc1", line 1183: Malformed conditional
> (${BUILDKERNELS:[)
> Unknown modifier '['
>
> "/usr/src/Makefile.inc1", line 1190: if-less endif
> bmake: fatal errors encountered -- cannot continue
> *** Error code 1
>
> Stop.
> make: stopped in /usr/src
> hellas# exit
> exit
>
> Script done on Thu Oct  6 23:37:00 2016
>
>  This just started happening after my machine had been down for a
> couple
> of days after a hang that damaged stuff in /usr/home.  I had already
> restored
> /usr/local from backups before narrowing down the weird behavior I was
> seeing
> in wmaker to /usr/home corruption.  So /usr/home has now been restored to
> good condition, too, but perhaps I need to restore something else as well.
> This mess was part of my justification to myself for the fresh checkout of
> /usr/src, but that doesn't seem to have made any difference in the
> buildworld
> failure.
>  If anyone else can see what's wrong and clue me in, I'd be grateful.
> I'm subscribed to the digest for this list, so please Cc: me directly, so
> I'll get replies right away.
> Thanks in advance!
>
>
>   Scott Bennett, Comm. ASMELG, CFIAG
>

Could something else have gotten corrupted?

> ls -i /bin/[
65795 /bin/[
> ls -i /bin/test
65795 /bin/test

The values (inode) will not match these, but must be identical.

'[' needs to be a hard link to test. I'm suspicious that something happened
to this link. If this is the case, other corruption may have occurred, but,
if you can re-create the hardlink (ln /bin/test /bin/[) and successfully
make buildworld  and make buildkernel, it's likely that you can reinstall
the system and the system will be fine. Of course, things could be damaged
in the installed ports, too.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: AIO not working on NFS share - ? Regression

[Kevin Oberman]

On Mon, Sep 5, 2016 at 1:41 PM, Jim Ohlstein <j...@ohlste.in> wrote:

> Hello,
>
> On 09/05/2016 04:34 PM, Konstantin Belousov wrote:
>
>> On Mon, Sep 05, 2016 at 02:26:30PM -0600, Alan Somers wrote:
>>
>>> Just to get your webserver out of the picture, could you please try
>>> running the aio test suite on an NFS share?  Do it like this:
>>> $ cd /usr/tests/sys/aio
>>> $ export TMPFS=/path/to/some/nfs/share
>>> $ kyua test
>>>
>> By default, unsafe aio is disabled, i.e. aio where the operation is not
>> really async and can usurp kernel thread for indefinite amount of time.
>> Non-local filesystems accesses are classified as unsafe, since their
>> completion is controlled by remote host.
>>
>
> Setting vfs.aio.enable_unsafe to 1 solved the problem, though I don't
> recall this being necessary in the past.
>
> Thanks for the quick responses and fix.
>
>
>
>>
>>> -Alan
>>>
>>> On Mon, Sep 5, 2016 at 2:14 PM, Jim Ohlstein <j...@ohlste.in> wrote:
>>>
>>>> Hello,
>>>>
>>>> For sometime now we've used a backend (non-internet accessible) server
>>>> to
>>>> generate static content that is shared via NFS to a front-end server for
>>>> internet access. Both machines use ZFS exclusively.
>>>>
>>>> The webserver is nginx and we had AIO set to on, with the AIO module
>>>> built
>>>> into the kernel.In 10.x it "just worked".
>>>>
>>>> About two weeks ago I upgraded that backend machine to 11-STABLE in
>>>> order to
>>>> start building packages for 11. I've just updated it again to r305417. I
>>>> don't recall it not working as expected.
>>>>
>>>> More recently I upgraded the front-end machine to 11-STABLE @r305311.
>>>> Since
>>>> then, AIO is not working and I get a critical error in the nginx logs
>>>> like
>>>> this:
>>>>
>>>> 2016/09/05 15:58:02 [crit] 21145#0: *649 aio_read("/path/to/file")
>>>> failed
>>>> (45: Operation not supported) while sending response to client ...
>>>>
>>>> In 11 AIO is built into the kernel by default, and I have confirmed
>>>> that it
>>>> works as expected in files from a local file system. Since the webserver
>>>> isn't aware that the file system in question is shared via NFS, it seems
>>>> this is an operating system issue.
>>>>
>>>
> --
> Jim Ohlstein
>

Could this also be related to AIO hanging VBox VMs? See
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212128
--
Kevin Oberman, Retired Network Engineer
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: leapsecond file

[Kevin Oberman]

On 11.0-BETA4 I have:
> grep expires /var/db/ntpd.leap-seconds.list
#File expires on:  1 Jun 2017

But I see what you do on 10.3-RELEASE.  Looks like the update has not made
it into 10 (an I would guess 9).


Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683

On Sun, Aug 7, 2016 at 7:31 PM, Randy Bush <ra...@psg.com> wrote:

> >> Aug  7 04:13:06 cache0 ntpd[576]: leapsecond file
> ('/var/db/ntpd.leap-seconds.list'): expired less than 68 days ago
> >>
> >> # grep ntp /etc/periodic.conf.local
> >> # 480.leapfile-ntpd
> >> daily_ntpd_leapfile_enable="YES"
> >> daily_ntpd_avoid_congestion="NO"
> >
> > For whatever reason, /etc/periodic/daily/480.leapfile-ntpd enters the
> > check phase on every invocation (daily), sleeps some random time less
> > than one day (if "avoid_congestion" true) and then decides that the file
> > is too young to replace (the current file expires June 1st, 2017). Logs
> > that to syslog .. rinse and repeat .. every day .. 
>
> /me is not understanding
>
> # grep expires /var/db/ntpd.leap-seconds.list
> #   File expires on:  1 Jun 2016
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

vt(4) issues on 11.0-BETA3 (Actually 11-STABLE)

[Kevin Oberman]

Running r303563 on a Lenovo T520 (Sandy Bridge).

I decided to cleanup /usr/local and delete all ports and rebuild all.
Things mostly worked and I'll report separately on what did not. After 2
days everything seems OK.

A particular annoyance during the update was vt(4).  If I had it to do
over, I'd have switched back to sc(4) for the ports re-build. I will file
bugs on these unless I can find ones already submitted.

1. ScrollLock is painfully broken. I press the key and scrolling stops, but
after some amount of data is written to the screen, the new data starts
overwriting the screen from the top. In a couple of seconds while building
ports, anything I'm trying to look at is gone! If I press ScrollLock again,
before the entire screen is overwritten, it resumes output right where it
left off at the bottom of the screen. I'm not too sure whether it starts
where it left off in hte data or with the next line after those that
over-wrote the screen.

2. If I select a region with the mouse (when not scrolling), at intervals
an area of the screen the size of that selected appears in reverse video.
This continues until I either select a different region or click to
deselect everything. (I strongly suspect that these two issues are in some
way related.)

3. After one port erred on the build, I scrolled back to select the list of
ports still to be built (a portmaster(8) feature) and try to paste it into
the same window or a different one. I get a totally different region. Since
the list spanned several lines due to line wrap, I got a bunch of other
lines, no doubt from some other part of the buffer. I have a hunch that
this is tied to the fact that a great many lines of output get wrapped into
multiple lines on the display and the arithmetic of what is selected goes
awry. (Just a guess, though.)

It is quite possible that all of these are actually different
manifestations of a single bug. I had never seen this before, but had never
used vt(4) for anything that produced such a number of wrapped lines. for
some builds, this resulted in a single line of text being wrapped to over a
dozen lines on the display.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Significant missing item in 11.0 release notes

[Kevin Oberman]

Thanks for the quick fix, Andrey! Now that this is taken care of, time to
start playing with the cool new features... especially naming tables.

Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683

On Mon, Aug 1, 2016 at 10:02 AM, Ian Smith <smi...@nimnet.asn.au> wrote:

> On Mon, 1 Aug 2016 18:47:37 +0300, Andrey V. Elsukov wrote:
>  > On 01.08.16 18:43, Ian Smith wrote:
>  > > Fast work Andrey, and sorry for rushing in.  I ASSumed, after reading
>  > > the new tables section in 11.0-R ipfw(8), that Kevin had run into:
>  > >
>  > >Tables require explicit creation via create before use.
>  > >
>  > > but diving - not too deeply - into the log of /head/sbin/ipfw/tables.c
>  > > from your commit, I think that statement must be out of date, at least
>  > > regarding existing ruleset table configuration?  Is that right?
>  >
>  > If you want to use some new specific feature you need to create table
>  > explicitly. But for old rules generic tables will be created
>  > automatically (with warning).
>
> Exactly how I was hoped it would work, thankyou ..
>
> cheers, Ian
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Significant missing item in 11.0 release notes

[Kevin Oberman]

This morning I updated my min user system from 10.3-Stable to 11.0-BETA3.
In general, things went well, but I had two issues that prevented the
network from operating. the first is a lack of documentation in the Release
Notes and the second is a driver issue. Since they are in no way related,
I'll send the report of the driver issue later.

I use ipfw(8) tables in my firewall configuration. Unfortunately, 11.0 has
introduced a totally re-worked tables structure. The new structure is
awesome and I read about it at the time the changes were being planned and
implemented, but had forgotten. As a result the very first line in my
configuration, "table 1 flush" was no longer valid and the remainder of the
file was ignored.

I assumed that I had missed this in the release notes, but I can find no
reference to this significant change that simultaneously greatly enhanced
ipfw table functionality, but also broke my configuration. While the fix
was trivial, if the Release Notes had addressed this, I would not have had
the problem in the first place.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: pkg(8) still not part of stable/11 (yet)???

[Kevin Oberman]

On Thu, Jul 28, 2016 at 12:09 PM, Miroslav Lachman <000.f...@quip.cz> wrote:

> Harry Schmalzbauer wrote on 07/28/2016 19:52:
>
>>   Hello,
>>
>> I just tried 11-beta2 – as usual, many thanks for all your hard work,
>> Devs and REs!
>>
>> I'm very concerned that there's still just a bootstrap-pkg :-(
>>
>
> [...]
>
> Please, don't ship FreeBSD 11 without a full version of pkg(8) in the base!
>>
>
> There are no plans to have pkg in base - not until base will be packaged
> too. (there are good reasons for this)
>
> Miroslav Lachman


And likely not then, either. pkg(8) is a rapidly evolving tool and only
updating it when there is a release is simply not viable. Until the
likelihood of an incompatible release of pkg(8) being more frequent than
releases on each supported branch, pkg(8) really has to stay out of base.

Yes, this is a real problem, though hardly an insurmountable one, but
putting pkg(8) in base right now or in the immediate future is simply not
practical. This has been re-stated many, many times on various mailing
lists. I'm sure that this is not the last time, either.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Two questions for FreeBSD 11: libgcc & pkg

[Kevin Oberman]

On Wed, Jul 27, 2016 at 10:42 AM, Matthieu Volat <ma...@alkumuna.eu> wrote:

> Hi, if somebody would be kind enough to educate me, I've two small
> questions about the 11 release.
>
>
> First, https://wiki.freebsd.org/WhatsNew/FreeBSD11 mention that libgcc
> was replaced by libcompiler_rt, yet after the freebsd-update
> upgrade/install/install/portmaster -af/install routine, I still have a
> (recently updated) libgcc:
>
>   # ls -l /lib/libgcc_s.so.1
>   -r--r--r--  1 root  wheel  56608 Jul 26 14:13 /lib/libgcc_s.so.1
>
> Is it normal?
>

I think so, but I am not sure. Is libcompiler_rt found? It seems likely the
old library is retrained for existing images linked to it while
libcompiler_rt is now used when new images are linked. (N.B. This is a
guess, though.)


> Second question is about the talks that the base system would be
> pkg-ized (https://wiki.freebsd.org/PkgBase). Do base pkgs share the same
> pkg database as ports pkgs? Can I now damage base installation with bad pkg
> usage?
>

I don't have the message handy, but several issues popped up that forced
the delay if the packaging of teh base system until at least 11.1. You can
probably look in the current@ archive to find the note.


> Thanks a lot for answers!
>
> --
> Matthieu Volat <ma...@alkumuna.eu>
>
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problem with FreeBSD-11.0-Beta1

[Kevin Oberman]

Filippo,

If you missed it, this is a known issue in BETA1.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211141
It was nothing you did wrong, but it does not look like there is a fix at
this time.

Please go to the FreeBSD Bugzilla <https://bugs.freebsd.org/bugzilla/> and
add your report to confirm that this is not a problem unique to a single
user.

Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683

On Fri, Jul 15, 2016 at 4:20 PM, Kevin Oberman <rkober...@gmail.com> wrote:

> On Fri, Jul 15, 2016 at 12:01 PM, Filippo Moretti via freebsd-stable <
> freebsd-stable@freebsd.org> wrote:
>
>> The system was installed as 11_CURRENT and I did not have any issue until
>> ALPHA-4.I did install everything from portsand I did install all of the
>> /etc during mergemaster and mergemaster -p.I do have a another disk with
>> 10.3-STABLE but I never tried to run applications from current in stable or
>> the other way.Filippops I did delete an old library I rebuilt windowmaker
>> and I have no complaint about it
>>
>>
> And, how did you go from ALPHA-4 to BETA-1? If you updated sources and
> rebuilt world and kernel, it should have been fine. If you tried
> freebsd-update, that might explain it as that method is documented as
> broken in BETA-1. I am uncertain what might happen if you tried this. I'd
> expect that the BETA-1 update files would have been removed.
>
> Somehow your password file seems to have lost all of the users since the
> move from ALPHA-4. I suspect /etc/group might have done the same, but I am
> not sure. You might merge all users from the 10.3 system using vipw(8) and
> do the same with your preferred to /etc/group. I have no idea what other
> things might be broken, though, nor how it happened (assuming you did not
> use freebsd-update).
>
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>
>
> On Friday, July 15, 2016 6:31 PM, Karl Denninger <k...@denninger.net>
>> wrote:
>>
>>
>>  On 7/15/2016 11:17, Kevin Oberman wrote:
>> > 11.0 has not been released. You are much more likely to get a useful
>> > response from current@.
>> >
>> > On Fri, Jul 15, 2016 at 5:09 AM, Filippo Moretti via freebsd-stable <
>> > freebsd-stable@freebsd.org> wrote:
>> >
>> >> I have the following problem when I start the system:
>> >
>> >
>> >> Unknown user name "avahi"  in message bus
>> >> configuration fileUnknown user name "polkitd"  in
>> message
>> >> bus configuration file
>> >> Unknown user name "polkitd"in message bus
>> >> configuration fileUnknown user name "colord"in
>> message
>> >> bus configuration file
>> >> Unknown user name "pulse"  in message bus
>> >> configuration fileUnknown user name "polkit"  in
>> >> message bus configuration file
>> > Unknown user name "haldaemon"in message bus configuration
>> file
>> >
>> > Failed to start message bus:
>> >
>> > Could not get VID and GID for username "messagebus"
>> >
>> > /etc/rc:Warning:failed to start dbus
>> >
>> > On the same computer I have a disk with 10.3_STABLE with the same
>> >> configuration files and everything is working properly.When in X  I
>> launch
>> >> firefox I get the following errorLibGL error:
>> > failed to open drm device:Permission denied
>> >
>> > LibGL error :failed to load driver: r 300
>> >
>> > This is very likely due to failure to start dbus
>> >
>> > sincerely
>> >
>> > Filippo
>> >
>> >
>> > Note: I have tried to recover the mail format above. Whatever mail tool
>> you
>> > used totally garbled things by removing line breaks.
>> >
>> > First, how did 11.0Beta-1 get installed? How sis your ports (X11, dbus,
>> > pulseaudio, etc.) get installed? When moving from one major release to
>> > another (10 to 11), you need to reinstall all ports/packages. The
>> > installation process is what creates these"users".
>> >
>> > It looks like you are just trying to run the things in /usr/local from
>> your
>> > 10.3 system. This

Re: Problem with FreeBSD-11.0-Beta1

[Kevin Oberman]

On Fri, Jul 15, 2016 at 12:01 PM, Filippo Moretti via freebsd-stable <
freebsd-stable@freebsd.org> wrote:

> The system was installed as 11_CURRENT and I did not have any issue until
> ALPHA-4.I did install everything from portsand I did install all of the
> /etc during mergemaster and mergemaster -p.I do have a another disk with
> 10.3-STABLE but I never tried to run applications from current in stable or
> the other way.Filippops I did delete an old library I rebuilt windowmaker
> and I have no complaint about it
>
>
And, how did you go from ALPHA-4 to BETA-1? If you updated sources and
rebuilt world and kernel, it should have been fine. If you tried
freebsd-update, that might explain it as that method is documented as
broken in BETA-1. I am uncertain what might happen if you tried this. I'd
expect that the BETA-1 update files would have been removed.

Somehow your password file seems to have lost all of the users since the
move from ALPHA-4. I suspect /etc/group might have done the same, but I am
not sure. You might merge all users from the 10.3 system using vipw(8) and
do the same with your preferred to /etc/group. I have no idea what other
things might be broken, though, nor how it happened (assuming you did not
use freebsd-update).
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


On Friday, July 15, 2016 6:31 PM, Karl Denninger <k...@denninger.net>
> wrote:
>
>
>  On 7/15/2016 11:17, Kevin Oberman wrote:
> > 11.0 has not been released. You are much more likely to get a useful
> > response from current@.
> >
> > On Fri, Jul 15, 2016 at 5:09 AM, Filippo Moretti via freebsd-stable <
> > freebsd-stable@freebsd.org> wrote:
> >
> >> I have the following problem when I start the system:
> >
> >
> >> Unknown user name "avahi"  in message bus
> >> configuration fileUnknown user name "polkitd"  in
> message
> >> bus configuration file
> >> Unknown user name "polkitd"in message bus
> >> configuration fileUnknown user name "colord"in
> message
> >> bus configuration file
> >> Unknown user name "pulse"  in message bus
> >> configuration fileUnknown user name "polkit"  in
> >> message bus configuration file
> > Unknown user name "haldaemon"in message bus configuration
> file
> >
> > Failed to start message bus:
> >
> > Could not get VID and GID for username "messagebus"
> >
> > /etc/rc:Warning:failed to start dbus
> >
> > On the same computer I have a disk with 10.3_STABLE with the same
> >> configuration files and everything is working properly.When in X  I
> launch
> >> firefox I get the following errorLibGL error:
> > failed to open drm device:Permission denied
> >
> > LibGL error :failed to load driver: r 300
> >
> > This is very likely due to failure to start dbus
> >
> > sincerely
> >
> > Filippo
> >
> >
> > Note: I have tried to recover the mail format above. Whatever mail tool
> you
> > used totally garbled things by removing line breaks.
> >
> > First, how did 11.0Beta-1 get installed? How sis your ports (X11, dbus,
> > pulseaudio, etc.) get installed? When moving from one major release to
> > another (10 to 11), you need to reinstall all ports/packages. The
> > installation process is what creates these"users".
> >
> > It looks like you are just trying to run the things in /usr/local from
> your
> > 10.3 system. This simply will not work.
> > --
> > Kevin Oberman, Part time kid herder and retired Network Engineer
> > E-mail: rkober...@gmail.com
> > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>
> Actually it SHOULD work unless you deleted the old libraries (in which
> case it definitely won't!); the dynamic loader is smart enough to do the
> right thing and load the correct (older) version of the shared libraries
> required.
>
> If this has been broken in recent releases IMHO that's not so good.
> There *are* instances where an older binary is all there is for a given
> application (e.g. from a vendor!) and thus backward compatibility when
> you roll forward the operating system is something that a lot of people
> (myself included) have both used and relied on for a very long time.
>
> Yes, I understand that you can't *count* on that working, particularly
> if the app in question makes explic

Re: Problem with FreeBSD-11.0-Beta1

[Kevin Oberman]

11.0 has not been released. You are much more likely to get a useful
response from current@.

On Fri, Jul 15, 2016 at 5:09 AM, Filippo Moretti via freebsd-stable <
freebsd-stable@freebsd.org> wrote:

> I have the following problem when I start the system:



> Unknown user name "avahi"  in message bus
> configuration fileUnknown user name "polkitd"   in message
> bus configuration file
> Unknown user name "polkitd"in message bus
> configuration fileUnknown user name "colord" in message
> bus configuration file
> Unknown user name "pulse"  in message bus
> configuration fileUnknown user name "polkit"  in
> message bus configuration file

Unknown user name "haldaemon"in message bus configuration file

Failed to start message bus:

Could not get VID and GID for username "messagebus"

/etc/rc:Warning:failed to start dbus

On the same computer I have a disk with 10.3_STABLE with the same
> configuration files and everything is working properly.When in X  I launch
> firefox I get the following errorLibGL error:

failed to open drm device:Permission denied

LibGL error :failed to load driver: r 300

This is very likely due to failure to start dbus

sincerely

Filippo


Note: I have tried to recover the mail format above. Whatever mail tool you
used totally garbled things by removing line breaks.

First, how did 11.0Beta-1 get installed? How sis your ports (X11, dbus,
pulseaudio, etc.) get installed? When moving from one major release to
another (10 to 11), you need to reinstall all ports/packages. The
installation process is what creates these"users".

It looks like you are just trying to run the things in /usr/local from your
10.3 system. This simply will not work.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: What are current dependencies of cd9660 kernel module?

[Kevin Oberman]

On Mon, Jun 27, 2016 at 11:53 AM, Jakub Lach <jakub_l...@mailplus.pl> wrote:

> Something changed in 10-STABLE, I had the same config for modules
> for a long time, and I cannot load cd9660 now,
>
> kernel: KLD cd9660.ko: depends on kernel - not available or version
> mismatch
> kernel: linker_load_file: Unsupported file type
>
> /boot/kernel $ ls -a
> . geom_md.ko  linker.hintsng_socket.ko
> snd_uaudio.ko   wlan_ccmp.ko
> ..i915kms.ko  msdosfs.ko  ng_tee.ko
>  udf.ko   wlan_tkip.ko
> cd9660.ko   if_ath.ko   netgraph.ko procfs.ko
>  uhci.ko wlan_wep.ko
> drm2.ko if_ath_pci.ko   ng_iface.ko pseudofs.ko umass.ko
> ehci.ko if_em.kong_ksocket.ko   rc4.ko  ums.ko
> fdescfs.ko  if_fwe.ko   ng_mppc.ko  sbp.ko  usb.ko
> firewire.ko if_fwip.ko  ng_ppp.ko   sbp_targ.ko wlan.ko
> fuse.ko kernel  ng_pptpgre.ko   snd_hda.ko
> wlan_amrr.ko
>

Check the dates on /boot/kernel/.kernl and /boot/kernel/cd9660.ko. It looks
like your kernel modules are not getting updated. Unless you elided a
portion of the "ls -a", a lot of modules are missing. There should be well
over 400 modules in /boot/kernel. CD9660 is also in GENERIC, so should be
in the kernel unless you have edited your conf to remove "options CD9660".

Looks like a bad "make buildkernel" or a really unusual configuration.
Dependencies are defined in /sys/conf/files*. There is a files and several
arch dependent files.arch files, but only the base /sys/conf/files
references CD9660 and I see no specific dependencies other than the kernel,
though, to actually use a CD, options like CAM are probably required.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: binary updates for 10.3 failing

[Kevin Oberman]

On Thu, May 5, 2016 at 9:07 AM, Andreas Ott <andr...@naund.org> wrote:

> Hi,
>
> I'm not sure if the stable list is the correct place to report this,
> but currently binary updates are not working. I see posts on the forum
> but no solutions are being offered (other than updates from source,
> which are difficult on production systems missing the src component).
> Something broke recently, it worked to update from RELEASE to -p1.
>
> Symptoms are like this (note that the system is -p1 already but the binay
> updater identifies it as -p0):
>
> [root@www ~]# freebsd-version
> 10.3-RELEASE-p1
> [root@www ~]# freebsd-update fetch
> src component not installed, skipped
> Looking up update.FreeBSD.org mirrors... none found.
> Fetching metadata signature for 10.3-RELEASE from update.FreeBSD.org...
> done.
> Fetching metadata index... done.
> Inspecting system... done.
> Preparing to download files... done.
>
> No updates needed to update system to 10.3-RELEASE-p0.
> [root@www ~]#
>
> I deleted /var/db/freebsd-update/* and tried again, same result.
>
> -andreas
> -
> Andreas Ott   K6OTT   +1.408.431.8727   andr...@naund.org
>

I am seeing the exact same issue. I really, really would like to get the
SSL fixes onto my web server, but I get the "No updates needed to update
system to 10.3-RELEASE-p0." message.

# freebsd-version -u -k
10.3-RELEASE
10.3-RELEASE-p1
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Sound from frontpanel connectors stopped working (10.3)

[Kevin Oberman]

On Mon, Mar 21, 2016 at 2:09 PM, Pasi Koivisto <pasi+free...@me.com> wrote:

>
> > On 21 Mar 2016, at 18:28, Pavel Timofeev <tim...@gmail.com> wrote:
> >
> > 21 марта 2016 г. 10:42 пользователь "Pavel Timofeev" <tim...@gmail.com>
> > написал:
> >>
> >> FreeBSD 10.3-RC3 stopped understand that I plugged my headphone in
> >> sound front panel connectors of my computer.
> >> I have two workstations with RC3. None of them works.
> >> It worked under 10.2-RELEASE.
> >>
> >> I can obtain more info to investigate it.
> >>
> >> Hope it will be fixed before the release
> >
> > Can anybody check and confirm/refute it?
>
> I am not sure if this is pertinent but it works on my laptop (lenovo x230)
> runnig 10.3-RC3.
>

No issues on my just updated ThinkPad T520.

How are you configuring the sound and what driver are you using?
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

10.2-Stable crash when VirtualBox VM running on suspend?

[Kevin Oberman]

I have twice had my laptop crash when I inadvertently had a Windows 7 VM
running at the time of the suspend.

I can certainly understand how this could happen, but should it? It's way
too easy to forget to "Save the machine state" before "zzz" and it sure is
annoying.

I am running r296404 with VB 4.3.36. I think I can generate a core if
someone would find it useful, though Murphy tells me that trying to do so
may fix the problem.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"