Re: svn commit: r333240 - in head/sys: powerpc/powerpc sys [appears to have broken the builds of head for riscv64]

[Mark Millard]

Conrad Meyer cem at freebsd.org wrote on
Sun May 6 22:32:13 UTC 2018, as part of a reply:

> P.S., Mark, your email server is misconfigured and most/all of your
> emails get flagged as spam.  I only saw this because I occasionally
> check the spam folder.

I wrote back directly indicating that I'd need evidence
in order to submit something to yahoo.com. Although, the
original was not sent directly to Conrad, so he likely
got the message directly from a freebsd-current server,
with a yahoo.com's Email server as an intermediate stage.
(I do not run my own servers.) The Email was composed
in macOS's Mail.app [V11.3 (3445.6.18)].

Of course, that reply was likely classified as spam.

If anyone else has such problems with the classification
of my Emails and can send material that would allow
reporting evidence to be submitted someplace, please do
so.

===
Mark Millard
marklmi26-fbsd at yahoo.com
( dsl-only.net went
away in early 2018-Mar)






___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: svn commit: r333240 - in head/sys: powerpc/powerpc sys [appears to have broken the builds of head for riscv64]

[Warner Losh]

What we really need to do is to make bcopy a wrapper around memmove on all
architectures, not just some. It's this lack of uniformity that's causing
problems.

Warner

On Sun, May 6, 2018 at 4:32 PM, Conrad Meyer  wrote:

> The same change as for powerpc needs to be made for riscv — the
> (bcopy) trick — to avoid expansion.
>
> Best,
> Conrad
>
> P.S., Mark, your email server is misconfigured and most/all of your
> emails get flagged as spam.  I only saw this because I occasionally
> check the spam folder.
>
> On Sat, May 5, 2018 at 4:39 PM, Mark Millard 
> wrote:
> > --- bcopy.o ---
> > In file included from /workspace/src/sys/riscv/riscv/bcopy.c:39:0:
> > /workspace/src/sys/sys/systm.h:262:31: error: expected identifier or
> '(' before '{' token
> >  #define bcopy(from, to, len) ({\
> >^
> > /workspace/src/sys/riscv/riscv/bcopy.c:134:1: note: in expansion of
> macro 'bcopy'
> >  bcopy(const void *src0, void *dst0, size_t length)
> >  ^
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: svn commit: r333240 - in head/sys: powerpc/powerpc sys [appears to have broken the builds of head for riscv64]

[Conrad Meyer]

The same change as for powerpc needs to be made for riscv — the
(bcopy) trick — to avoid expansion.

Best,
Conrad

P.S., Mark, your email server is misconfigured and most/all of your
emails get flagged as spam.  I only saw this because I occasionally
check the spam folder.

On Sat, May 5, 2018 at 4:39 PM, Mark Millard  wrote:
> --- bcopy.o ---
> In file included from /workspace/src/sys/riscv/riscv/bcopy.c:39:0:
> /workspace/src/sys/sys/systm.h:262:31: error: expected identifier or '(' 
> before '{' token
>  #define bcopy(from, to, len) ({\
>^
> /workspace/src/sys/riscv/riscv/bcopy.c:134:1: note: in expansion of macro 
> 'bcopy'
>  bcopy(const void *src0, void *dst0, size_t length)
>  ^
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: IGNORE_OSVERSION=yes -- can't install pkg

[Boris Samorodov]

05.05.2018 18:26, Chris H пишет:
> On Fri, 04 May 2018 22:57:52 -0700  said
> 
>> I just setup a jail from a 12-CURRENT I built awhile ago. It has no ports
>> tree. So I'm attempting
>> to install svnlite. issuing pkg search svnlite returns
>> The package management tool is not yet installed on your system.
>> Do you want to fetch and install it now? [y/N]: y
>> Bootstrapping pkg from
>> pkg+http://pkg.FreeBSD.org/FreeBSD:12:amd64/latest,
>> please wait...
>> Verifying signature with trusted certificate
>> pkg.freebsd.org.2013102301...
>> done
>> [12current.localhost] Installing pkg-1.10.5...
>> Newer FreeBSD version for package pkg:
>> To ignore this error set IGNORE_OSVERSION=yes
>> - package: 1200062
>> - running kernel: 1200054
>> Allow missmatch now?[Y/n]:
>>
>> Umm, what? Should I ignore this error? If so, why is there an error at
>> all?
>> I answered no. Guess I won't be able to use pkg(8) on this jail(8). :-(
>>
>> --Chris
> OK the only reference[1] I can find regarding this, indicates that
> answering "Y"
> to Allow missmatch now? resulted in an ABI mismatch that caused pkg(8)
> to be
> unusable.
> This is on an older version of 12, so I don't have anything that might have
> appeared in UPDATING. I really need this jail to resolve accumulating
> pr(1)'s
> on ports(7) I maintain.

FreeBSD project has packages for the latest HEAD. But you may build your
own packages via poudriere. First, build the needed base system, then
build needed packages.

-- 
WBR, bsam
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Regression Resume Lenovo T450

[Manuel Stühn]

On Fri, May 04, 2018 at 08:07:17AM +0200, Manuel Stühn wrote:


Since some time now CURRENT runs very smoothly on my Lenovo T450 in
conjunction with drm-stable-kmod installed. WLAN, Suspense worked
out of the box (at least ... until now). Due to pkg(8) complaining about
wrong ABI of packages, I've made an update from r332385 (1200061) to
r333091 (1200062), and now the T450 does not resume anymore; i have to
hold the power button for some time to power it down. The
ZFS-Boot-Environment I've made beforehand updating is still capable of
resuming.

I tried to find out which commit broke the resume for me by installing
older kernels, but even installing r332385 kernel (into the actual
r333091 userland) does not restore its capability to resume.



Some more testing has happened:

Since I have a BootEnvironment capable of suspend/resume, I've tried 
some combinations of kernels (in fact, whole boot-folders) and 
unserlands. I copied the boot-folder from the BE r332385 (which works) 
into the current BE and restarted. This combination was NOT able to 
resume. But the other way around is (current boot-folder (r333091) in 
the r332385 based BootEnvironment)


It seems to me, that not the kernel but either some change in userland 
or package broke the resume somehow. But I do not have a clue, which of 
those even can impact the resume procedure at all. Two packages came to 
my mind:


1. graphics/drm-stable-kmod, but the installed packages are identical 
for both, the "old" and the current BE. (both packages are installed 
from ports along with the respective buildworld+buildkernel)


2. The firmwares used by sysutils/cpupdate, but after replacing the 
firmware files with the firmwares from the old BE resume still doesn't 
work.


Any ideas?

--
Manuel

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"