signal 11 for 'conftest' && poudriere jails

2019-06-16 Thread Matthias Apitz

While running poudriere jails on a very recent CURRENT:

FreeBSD jet 13.0-CURRENT FreeBSD 13.0-CURRENT #1 r349041: Sat Jun 15 07:45:13 
CEST 2019 guru@jet:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64

I see messages about signal 11 for 'conftest'. The uid 65534 (nobody)
let me think in poudriere, because there is nothing else running on this
box:

Jun 16 19:31:46 jet kernel: pid 55572 (conftest), jid 23, uid 65534: exited on 
signal 11 (core dumped)
Jun 16 19:37:25 jet su[98388]: guru to root on /dev/pts/2
Jun 16 20:01:32 jet kernel: pid 26452 (conftest), jid 25, uid 65534: exited on 
signal 11 (core dumped)
Jun 16 20:02:26 jet kernel: pid 54189 (conftest), jid 25, uid 65534: exited on 
signal 11 (core dumped)
Jun 16 20:14:09 jet kernel: pid 86215 (conftest), jid 23, uid 65534: exited on 
signal 11 (core dumped)
Jun 16 20:31:06 jet ntpdate[79734]: step time server 130.149.17.21 offset 
0.309740 sec
Jun 16 20:38:39 jet kernel: pid 61044 (conftest), jid 25, uid 65534: exited on 
signal 11 (core dumped)
Jun 16 20:45:29 jet kernel: pid 24274 (conftest), jid 31, uid 65534: exited on 
signal 11 (core dumped)
Jun 16 21:31:06 jet ntpdate[99262]: step time server 130.149.17.21 offset 
0.309141 sec
Jun 16 22:31:06 jet ntpdate[27064]: step time server 130.149.17.21 offset 
0.309090 sec
Jun 16 23:31:06 jet ntpdate[1088]: step time server 130.149.17.21 offset 
0.309793 sec
Jun 16 23:51:38 jet kernel: pid 10847 (java), jid 29, uid 65534, was killed: 
out of swap space
Jun 17 00:31:06 jet ntpdate[6936]: step time server 130.149.17.21 offset 
0.308939 sec
Jun 17 00:32:58 jet su[10397]: guru to root on /dev/pts/4
Jun 17 00:38:22 jet su[28548]: guru to root on /dev/pts/2
Jun 17 01:31:06 jet ntpdate[39553]: step time server 130.149.17.21 offset 
0.309018 sec
Jun 17 01:41:23 jet kernel: pid 81104 (conftest), jid 26, uid 65534: exited on 
signal 11 (core dumped)
Jun 17 02:17:29 jet kernel: pid 9625 (conftest), jid 29, uid 65534: exited on 
signal 11 (core dumped)
Jun 17 02:21:56 jet kernel: pid 36351 (conftest), jid 29, uid 65534: exited on 
signal 11 (core dumped)

What does this mean? What is 'conftest' at all?

matthias
...
-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
May, 9: Спаси́бо освободители! Thank you very much, Russian liberators!


signature.asc
Description: PGP signature


Re: building x11-wm/plasma5-kwin w/ poudriere results in out of swap space

2019-06-13 Thread Matthias Apitz
El día Thursday, June 13, 2019 a las 04:38:25PM +0800, Martin Wilke escribió:

> On 2019-06-11 14:59, Matthias Apitz wrote:
> >Hello,
> >
> >I'm build the latest port svn checkout (June 10) on r342378 with
> >poudriere and (after isolating it) have the problem that building
> >x11-wm/plasma5-kwin runs reproducible out of swap during 'configure'
> >phase:
> >
> >[00:00:49] Cleaning the build queue
> >[00:00:49] Sanity checking build queue
> >[00:00:49] Processing PRIORITY_BOOST
> >[00:00:50] Balancing pool
> >[00:00:50] Recording filesystem state for prepkg... done
> >[00:00:52] Building 1 packages using 1 builders
> >[00:00:52] Starting/Cloning builders
> >[00:00:54] Hit CTRL+t at any time to see build progress and stats
> >[00:00:54] [01] [00:00:00] Building x11-wm/plasma5-kwin |
> >plasma5-kwin-5.15.5
> >load: 0.95  cmd: sh 19376 [piperd] 67.68r 0.00u 0.00s 0% 3932k
> >[freebsd-r342378-ports-20190610] [2019-06-11_07h49m10s]
> >[parallel_build:] Queued: 1  Built: 0  Failed: 0  Skipped: 0  Ignored:
> >0  Tobuild: 1   Time: 00:01:40
> > [01]: x11-wm/plasma5-kwin   | plasma5-kwin-5.15.5
> >build-depends   (00:01:06 / 00:01:08)
> >[00:02:02] Logs:
> >/usr/local/poudriere/data/logs/bulk/freebsd-r342378-ports-20190610/2019-06-11_07h49m10s
> >load: 0.52  cmd: wc 26535 [piperd] 0.10r 0.00u 0.00s 0% 2656k
> >[freebsd-r342378-ports-20190610] [2019-06-11_07h49m10s]
> >[parallel_build:] Queued: 1  Built: 0  Failed: 0  Skipped: 0  Ignored:
> >0  Tobuild: 1   Time: 00:03:27
> > [01]: x11-wm/plasma5-kwin   | plasma5-kwin-5.15.5   configure
> >  (00:01:17 / 00:02:55)
> >[00:03:49] Logs:
> >/usr/local/poudriere/data/logs/bulk/freebsd-r342378-ports-20190610/2019-06-11_07h49m10s
> >^C[00:04:13] Error: Signal SIGINT caught, cleaning up and exiting
> >
> >Is this a known issue? Or should I investigate deeper which process it
> >is?
> 
> This problem is not only for plasma5 its random happened since import of
> clang8. I have not found any real solution for it.

Hello Martin,

Thanks for replying. The issue is not randomly, but affects all ports
using a QML tool 'qmlplugindump' which allocates 12 GByte memory. It is
this bug issue:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232736

I attached yesterday a poudriere log file for the port misc/kf5-purpose
which also shows the same problem with 'qmlplugindump'. The poudriere
log also says, that clang7 is used:

...
===
===>  Configuring for kf5-purpose-5.58.0
===>  Performing out-of-source build
/bin/mkdir -p /wrkdirs/usr/ports/misc/kf5-purpose/work/.build
-- The C compiler identification is Clang 7.0.1
-- The CXX compiler identification is Clang 7.0.1
-- Check for working C compiler: /usr/bin/clang
-- Check for working C compiler: /usr/bin/clang -- works
...

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
May, 9: Спаси́бо освободители! Thank you very much, Russian liberators!
___
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"


building x11-wm/plasma5-kwin w/ poudriere results in out of swap space

2019-06-11 Thread Matthias Apitz

Hello,

I'm build the latest port svn checkout (June 10) on r342378 with
poudriere and (after isolating it) have the problem that building
x11-wm/plasma5-kwin runs reproducible out of swap during 'configure'
phase:

[00:00:49] Cleaning the build queue
[00:00:49] Sanity checking build queue
[00:00:49] Processing PRIORITY_BOOST
[00:00:50] Balancing pool
[00:00:50] Recording filesystem state for prepkg... done
[00:00:52] Building 1 packages using 1 builders
[00:00:52] Starting/Cloning builders
[00:00:54] Hit CTRL+t at any time to see build progress and stats
[00:00:54] [01] [00:00:00] Building x11-wm/plasma5-kwin | plasma5-kwin-5.15.5
load: 0.95  cmd: sh 19376 [piperd] 67.68r 0.00u 0.00s 0% 3932k
[freebsd-r342378-ports-20190610] [2019-06-11_07h49m10s] [parallel_build:] 
Queued: 1  Built: 0  Failed: 0  Skipped: 0  Ignored: 0  Tobuild: 1   Time: 
00:01:40
[01]: x11-wm/plasma5-kwin   | plasma5-kwin-5.15.5   
build-depends   (00:01:06 / 00:01:08)
[00:02:02] Logs: 
/usr/local/poudriere/data/logs/bulk/freebsd-r342378-ports-20190610/2019-06-11_07h49m10s
load: 0.52  cmd: wc 26535 [piperd] 0.10r 0.00u 0.00s 0% 2656k
[freebsd-r342378-ports-20190610] [2019-06-11_07h49m10s] [parallel_build:] 
Queued: 1  Built: 0  Failed: 0  Skipped: 0  Ignored: 0  Tobuild: 1   Time: 
00:03:27
[01]: x11-wm/plasma5-kwin   | plasma5-kwin-5.15.5   configure   
(00:01:17 / 00:02:55)
[00:03:49] Logs: 
/usr/local/poudriere/data/logs/bulk/freebsd-r342378-ports-20190610/2019-06-11_07h49m10s
^C[00:04:13] Error: Signal SIGINT caught, cleaning up and exiting

Is this a known issue? Or should I investigate deeper which process it
is?

matthias


-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
May, 9: Спаси́бо освободители! Thank you very much, Russian liberators!



- End forwarded message -

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
May, 9: Спаси́бо освободители! Thank you very much, Russian liberators!
___
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: FreeBSD and Coreboot

2019-05-27 Thread Matthias Apitz
El día Monday, May 27, 2019 a las 11:13:46AM -0400, Eric McCorkle escribió:

> Hello everyone,
> 
> I'm through enough of my job change that I can start working on FreeBSD
> again.  One thing I've had on my list to examine is using FreeBSD with
> coreboot, so I wanted to put out a call for anyone who has done work on
> this, or knows anything about it.

Hello Eric,

I don't know if this is something which has to do with your project.
Since 2015 I use an Acer C720 Chromebook with FreeBSD (CURRENT) this has
AFAIK coreboot with SeaBIOS and works just fine.

Just to let you know.

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
May, 9: Спаси́бо освободители! Thank you very much, Russian liberators!
___
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: CFT: FreeBSD Package Base

2019-04-29 Thread Matthias Apitz

Why this thread has to go to all these lists? I receive any mail 5
times!

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
N € I N zur EU!
"Gegen das EU-Europa der Banken, Konzerne und Kriegstreiber.
Für ein soziales und friedliches Europa der Völker." DKP


signature.asc
Description: PGP signature


Re: uname -a output without svn revision number

2019-01-04 Thread Matthias Apitz
El día viernes, enero 04, 2019 a las 09:30:05a. m. -0500, Ed Maste escribió:

> It looks like some aspects of this have been broken since r308789. Do
> you happen to have a git or hg tree higher up in the directory
> hierarchy? For example, ~/.git, and ~/src/freebsd/...? I'll have a fix
> for that case soon.

No, nothing.

> 
> If that's not the case, please run (from the src toplevel dir)
> 
> sh -x sys/conf/newvers.sh >newvers.log 2>&1

I looked into the script  sys/conf/newvers.sh and I think I understand
now the problem. I compiled /usr/src on some other faster server and
moved /usr/src and /usr/obj to my netbook as tar-archive to update
kernel and userland there. To save space on the netbook
I excluded /usr/src/.svn which is causing now the absence of the
revision number.

    matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, 
Druschba
instead of Nazis, to live instead of to survive.


signature.asc
Description: PGP signature


Re: uname -a output without svn revision number

2019-01-03 Thread Matthias Apitz
El día viernes, enero 04, 2019 a las 07:52:40a. m. +0100, Dimitry Andric 
escribió:

> On 4 Jan 2019, at 06:52, Matthias Apitz  wrote:
> > 
> > I've compiled CURRENT from svn and this gave me as 'uname -a' output:
> > 
> > FreeBSD c720-r342378 13.0-CURRENT FreeBSD 13.0-CURRENT r342378 GENERIC  
> > amd64
> > 
> > Now I've had do modify a source file (to nail down some problem) and the
> > revision number went away from the output; it now says:
> > 
> > FreeBSD c720-r342378 13.0-CURRENT FreeBSD 13.0-CURRENT GENERIC  amd64
> > 
> > Why is this? I've read in UPDATING that:
> > 
> > ...
> > 
> > But this does not explain why now the SVN revision number went away.
> 
> For me, it doesn't go away, but shows an "M" suffix, instead.  In
> /usr/obj/usr/src/sys/GENERIC/vers.c it shows:
> 
> #define VERSTR "FreeBSD 13.0-CURRENT r342593M \n"
> 
> What is the output of sh /usr/src/sys/conf/newvers.sh for you?

$ ls -l /usr/obj/usr/src/amd64.amd64/sys/GENERIC/vers.c
-rw-r--r--  1 root  wheel  1919  3 ene.  11:59 
/usr/obj/usr/src/amd64.amd64/sys/GENERIC/vers.c
$ tail -12 /usr/obj/usr/src/amd64.amd64/sys/GENERIC/vers.c

#define SCCSSTR "@(#)FreeBSD 13.0-CURRENT GENERIC"
#define VERSTR "FreeBSD 13.0-CURRENT GENERIC\n"
#define RELSTR "13.0-CURRENT"

char sccs[sizeof(SCCSSTR) > 128 ? sizeof(SCCSSTR) : 128] = SCCSSTR;
char version[sizeof(VERSTR) > 256 ? sizeof(VERSTR) : 256] = VERSTR;
char compiler_version[] = "FreeBSD clang version 7.0.1 (tags/RELEASE_701/final 
349250) (based on LLVM 7.0.1)";
char ostype[] = "FreeBSD";
char osrelease[sizeof(RELSTR) > 32 ? sizeof(RELSTR) : 32] = RELSTR;
int osreldate = 135;
char kern_ident[] = "GENERIC";
$ sh /usr/src/sys/conf/newvers.sh

I did around 11:50 am (i.e. the mod time of vers.c matches) a 'make buildkernel 
NO_CLEAN=yes'

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, 
Druschba
instead of Nazis, to live instead of to survive.


signature.asc
Description: PGP signature


uname -a output without svn revision number

2019-01-03 Thread Matthias Apitz

Hello,

I've compiled CURRENT from svn and this gave me as 'uname -a' output:

FreeBSD c720-r342378 13.0-CURRENT FreeBSD 13.0-CURRENT r342378 GENERIC  amd64

Now I've had do modify a source file (to nail down some problem) and the
revision number went away from the output; it now says:

FreeBSD c720-r342378 13.0-CURRENT FreeBSD 13.0-CURRENT GENERIC  amd64

Why is this? I've read in UPDATING that:

...
20180913:
Reproducible build mode is now on by default, in preparation for
FreeBSD 12.0.  This eliminates build metadata such as the user,
host, and time from the kernel (and uname), unless the working tree
corresponds to a modified checkout from a version control system.
The previous behavior can be obtained by setting the /etc/src.conf
knob WITHOUT_REPRODUCIBLE_BUILD.
...

But this does not explain why now the SVN revision number went away.

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, 
Druschba
instead of Nazis, to live instead of to survive.


signature.asc
Description: PGP signature


Re: r342378: usbconfig takes 3-5 minutes to read the bus

2019-01-02 Thread Matthias Apitz
El día miércoles, enero 02, 2019 a las 12:37:37p. m. +0100, Hans Petter Selasky 
escribió:

> > Nothing. Only on boot it sees the card:
> 
> And you are using the latest version of pcsd ?

Yes. Compiled with all ports from December 23.

> 
> > Jan  2 11:25:39 c720-r342378 kernel: ugen0.1: <0x8086 XHCI root HUB> at 
> > usbus0
> > Jan  2 11:25:39 c720-r342378 kernel: ugen1.1:  at 
> > usbus1
> > Jan  2 11:25:39 c720-r342378 kernel: ugen1.2:  > 0x8000> at usbus1
> > Jan  2 11:25:39 c720-r342378 kernel: ugen0.2:  at 
> > usbus0
> > Jan  2 11:25:39 c720-r342378 kernel: ugen0.3:  > 0xe056> at usbus0
> > Jan  2 11:25:39 c720-r342378 kernel: ugen0.4:  > Token> at usbus0
> 
> There has been some changes in libusb recently .

After card removal and insert devd(8) starts a new pcsd:

Jan  2 16:39:11 c720-r342378 kernel: ugen0.4:  at usbus0
Jan  2 16:39:11 c720-r342378 root[13636]: CCID uTrust, type: ATTACH, system: 
USB, subsystem: INTERFACE
Jan  2 16:39:11 c720-r342378 root[13637]: /usr/local/sbin/pcscd --debug 
--foreground

This sits hanging on /dev/usb/1.1.0:

# lsof -p 13639
COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
pcscd   13639 root  cwd   VDIR  0,113 10242 /
pcscd   13639 root  rtd   VDIR  0,113 10242 /
pcscd   13639 root  txt   VREG  0,113   121992 15279826 
/usr/local/sbin/pcscd
pcscd   13639 root  txt   VREG  0,113   151560 29294355 
/libexec/ld-elf.so.1
pcscd   13639 root  txt   VREG  0,11398016 29294906 
/usr/lib/libusb.so.3
pcscd   13639 root  txt   VREG  0,11327640 29294864 
/usr/lib/librt.so.1
pcscd   13639 root  txt   VREG  0,113   135712 29293769 
/lib/libthr.so.3
pcscd   13639 root  txt   VREG  0,113  2063072 29294412 
/lib/libc.so.7
pcscd   13639 root0r  VCHR   0,43  0t0   43 /dev/null
pcscd   13639 root1u  VCHR   0,43  0t0   43 /dev/null
pcscd   13639 root2u  VCHR   0,43  0t0   43 /dev/null
pcscd   13639 root3u  unix 0xf800609ff6d0  0t0  
->0xf800163fa368
pcscd   13639 root4u  PIPE 0xf8004f13c2f816384  
->0xf8004f13c460
pcscd   13639 root5u  PIPE 0xf8004f13c4600  
->0xf8004f13c2f8
pcscd   13639 root6u  unix 0xf80072b03a38  0t0  
/var/run/pcscd/pcscd.comm
pcscd   13639 root7u  PIPE 0xf8004e5422f816384  
->0xf8004e542460
pcscd   13639 root8u  PIPE 0xf8004e5424600  
->0xf8004e5422f8
pcscd   13639 root9u  PIPE 0xf8004e50900016384  
->0xf8004e509168
pcscd   13639 root   10u  PIPE 0xf8004e5091680  
->0xf8004e509000
pcscd   13639 root   11u  VCHR   0,52  0t0   52 
/dev/usb/1.1.0
pcscd   13639 root   12u  VCHR   0,52  0t0   52 
/dev/usb/1.1.0

(note: the older working proc had open /dev/usb/0.4.0)

> What does "procstat -ak" output. Does it hang on any "usb" functions?

# ps ax | grep pcs
13639  -  I  0:00,01 /usr/local/sbin/pcscd --debug --foreground
13967  4  S+ 0:00,01 grep pcs

# procstat -k 13639
  PIDTID COMMTDNAME  KSTACK
13639 100287 pcscd   -   mi_switch sleepq_switch 
sleepq_catch_signals sleepq_wait_sig _sleep pipe_read dofileread kern_readv 
sys_read amd64_syscall fast_syscall_common
13639 100821 pcscd   -   mi_switch sleepq_switch 
sleepq_catch_signals sleepq_wait_sig _sleep pipe_read dofileread kern_readv 
sys_read amd64_syscall fast_syscall_common
13639 100822 pcscd   -   mi_switch sleepq_switch 
sleepq_catch_signals sleepq_wait_sig _sx_xlock_hard _sx_xlock 
usbd_enum_lock_sig usb_ref_device usb_open devfs_open VOP_OPEN_APV 
vn_open_vnode vn_open_cred kern_openat amd64_syscall fast_syscall_common

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, 
Druschba
instead of Nazis, to live instead of to survive.
___
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: r342378: usbconfig takes 3-5 minutes to read the bus

2019-01-02 Thread Matthias Apitz
El día miércoles, enero 02, 2019 a las 09:44:06a. m. +0100, Hans Petter Selasky 
escribió:

> On 1/1/19 2:51 PM, Matthias Apitz wrote:
> > Now with r342378, it works only after boot but not after withdraw/re-insert
> > anymore. To separate the problem from GnuPG and it's software stack, I have 
> > here some
> > small tests with usbconfig(8). First usbconfig reads fine the bus, but then
> > it takes 3-5 minutes to get any results, see below.
> 
> Did you update the user-space libusb aswell?

I did a complete 'make installworld' and they look updated:

$ ls -l /usr/lib/libusb*
-r--r--r--  1 root  wheel  573256 31 dic.  12:19 /usr/lib/libusb_p.a
-r--r--r--  1 root  wheel  541506 31 dic.  12:19 /usr/lib/libusb.a
lrwxr-xr-x  1 root  wheel  11 31 dic.  12:33 /usr/lib/libusb.so -> 
libusb.so.3
-r--r--r--  1 root  wheel   98016 31 dic.  12:33 /usr/lib/libusb.so.3
-r--r--r--  1 root  wheel   73910 31 dic.  12:19 /usr/lib/libusbhid_p.a
-r--r--r--  1 root  wheel   71390 31 dic.  12:19 /usr/lib/libusbhid.a
lrwxr-xr-x  1 root  wheel  14 31 dic.  12:33 /usr/lib/libusbhid.so -> 
libusbhid.so.4
-r--r--r--  1 root  wheel   23720 31 dic.  12:33 /usr/lib/libusbhid.so.4

At boot time a process is launched by devd(8) which reads the OpenPGP
card and this works fine and has the device open:

$ ps ax | grep pcs
 501 v0- S 0:00,22 /usr/local/sbin/pcscd --debug --foreground

# lsof -p 501
COMMAND PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
pcscd   501 root  cwd   VDIR  0,113 10242 /
pcscd   501 root  rtd   VDIR  0,113 10242 /
pcscd   501 root  txt   VREG  0,113   121992 15279826 
/usr/local/sbin/pcscd
pcscd   501 root  txt   VREG  0,113   151560 29294355 
/libexec/ld-elf.so.1
pcscd   501 root  txt   VREG  0,11398016 29294906 
/usr/lib/libusb.so.3
pcscd   501 root  txt   VREG  0,11327640 29294864 
/usr/lib/librt.so.1
pcscd   501 root  txt   VREG  0,113   135712 29293769 
/lib/libthr.so.3
pcscd   501 root  txt   VREG  0,113  2063072 29294412 /lib/libc.so.7
pcscd   501 root  txt   VREG  0,113   135192 1905 
/usr/local/lib/pcsc/drivers/ifd-ccid.bundle/Contents/FreeBSD/libccid.so
pcscd   501 root0r  VCHR   0,43  0t0   43 /dev/null
pcscd   501 root1u  VREG  0,113 3568882411580 / 
(/dev/ada0p2)
pcscd   501 root2u  VREG  0,113 3568882411580 / 
(/dev/ada0p2)
pcscd   501 root3u  VREG  0,113 3568882411580 / 
(/dev/ada0p2)
pcscd   501 root4u  PIPE 0xf800162fd8e816384  
->0xf800162fda50
pcscd   501 root5u  PIPE 0xf800162fda500  
->0xf800162fd8e8
pcscd   501 root6u  unix 0xf800164036d0  0t0  
/var/run/pcscd/pcscd.comm
pcscd   501 root7u  unix 0xf80016feaa38  0t0  
/var/run/pcscd/pcscd.comm
pcscd   501 root9u  PIPE 0xf800162fd2f816384  
->0xf800162fd460, cnt=2, in=2
pcscd   501 root   10u  PIPE 0xf800162fd4600  
->0xf800162fd2f8
pcscd   501 root   11u  PIPE 0xf800162f28e816384  
->0xf800162f2a50
pcscd   501 root   12u  PIPE 0xf800162f2a500  
->0xf800162f28e8
pcscd   501 root   13u  VCHR   0,87  0t0   87 /dev/usb/0.4.0
pcscd   501 root   14u  VCHR   0,87  0t0   87 /dev/usb/0.4.0

$ gpg2 --card-status
Reader ...: Identiv uTrust 3512 SAM slot Token (55511725600891) 00 00
Application ID ...: D2760001240102010005532B
Version ..: 2.1
Manufacturer .: ZeitControl
Serial number : 532B
Name of cardholder: Matthias Apitz
...


When I withdraw the OpenPGP card devd(8) hooks kill that proc and
restarts a new one on card insert. But this new proc hangs. 

The same happens when I disable the devd(8) start of this proc and start
the same proc from a shell (for debugging). This hangs too.

Looks like something makes the USB stack broken after the point where
devd(8) can launch fine the first proc of pcscd.

> Any error messages in dmesg?

Nothing. Only on boot it sees the card:

Jan  2 11:25:39 c720-r342378 kernel: ugen0.1: <0x8086 XHCI root HUB> at usbus0
Jan  2 11:25:39 c720-r342378 kernel: ugen1.1:  at usbus1
Jan  2 11:25:39 c720-r342378 kernel: ugen1.2:  at 
usbus1
Jan  2 11:25:39 c720-r342378 kernel: ugen0.2:  at 
usbus0
Jan  2 11:25:39 c720-r342378 kernel: ugen0.3:  at 
usbus0
Jan  2 11:25:39 c720-r342378 kernel: ugen0.4:  at usbus0

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, 
Druschba
instead of Nazis, to live instead of to survive.


signature.asc
Description: PGP signature


Re: ld-elf.so.1: /usr/local/lib/libglib-2.0.so.0: Undefined symbol "environ"

2019-01-01 Thread Matthias Apitz
El día viernes, diciembre 28, 2018 a las 12:55:32p. m. -0800, Cy Schubert 
escribió:

> In message  il.com>
> , Antoine Brodin writes:
> > On Fri, Dec 28, 2018 at 8:39 PM Graham Perrin  
> > wrote:
> > >
> > > On Fri, 28 Dec 2018 at 16:31, Emiel Kollof  
> > > wrot
> > e:
> > >
> > > > Confirmed with Chromium on my CURRENT box:
> > >
> > > …
> > >
> > > Thanks folks. Should I report it as a bug with devel/glib20?
> >
> > Hi,
> >
> > I think it's a regression in the toolchain (the problem doesn't occur
> > on 11.2 or 12.0),  so it should be reported to freebsd-toolchain@
> 
> No issue here however I rebuilt glib on Dec 21.

I see the same with www/chromium on r342378 and ports, both from Dec 23.

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, 
Druschba
instead of Nazis, to live instead of to survive.


signature.asc
Description: PGP signature


r342378: usbconfig takes 3-5 minutes to read the bus

2019-01-01 Thread Matthias Apitz


I updated my amd64 laptop Acer C720 from r314251 to r342378. The OpenPGP Card 
HID Global OMNIKEY 6121 was working in r314251 nicely and after withdraw and
re-insert GnuPG was just asking for the PIN again and access to the ciphered
material or signing keys was fine.

Now with r342378, it works only after boot but not after withdraw/re-insert
anymore. To separate the problem from GnuPG and it's software stack, I have 
here some
small tests with usbconfig(8). First usbconfig reads fine the bus, but then
it takes 3-5 minutes to get any results, see below.

Please, what can I check or enable to get additional logs for the problem.

Thanks


# uname -a
FreeBSD c720-r342378 13.0-CURRENT FreeBSD 13.0-CURRENT r342378 GENERIC  amd64


# usbconfig list
ugen1.1:  at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) 
pwr=SAVE (0mA)
ugen0.1: <0x8086 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) 
pwr=SAVE (0mA)
ugen0.2:  at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) 
pwr=ON (500mA)
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 (100mA)
ugen0.4:  at usbus0, cfg=0 md=HOST 
spd=FULL (12Mbps) pwr=ON (100mA)


# usbconfig -d ugen0.4 list
ugen0.4:  at usbus0, cfg=0 md=HOST 
spd=FULL (12Mbps) pwr=ON (100mA)


# usbconfig -d ugen0.4 dump_device_desc
ugen0.4:  at usbus0, cfg=0 md=HOST 
spd=FULL (12Mbps) pwr=ON (100mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0200
  bDeviceClass = 0x  
  bDeviceSubClass = 0x
  bDeviceProtocol = 0x
  bMaxPacketSize0 = 0x0008
  idVendor = 0x076b
  idProduct = 0x6632
  bcdDevice = 0x0103
  iManufacturer = 0x0001  
  iProduct = 0x0002  
  iSerialNumber = 0x  
  bNumConfigurations = 0x0001


From now it takes 3++ minutes to get the information from USB:

# date ; usbconfig -d ugen0.4 dump_device_desc ; date
Tue Jan  1 11:51:55 CET 2019
ugen0.4:  at usbus0, cfg=0 md=HOST 
spd=FULL (12Mbps) pwr=ON (100mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0200
  bDeviceClass = 0x  
  bDeviceSubClass = 0x
  bDeviceProtocol = 0x
  bMaxPacketSize0 = 0x0008
  idVendor = 0x076b
  idProduct = 0x6632
  bcdDevice = 0x0103
  iManufacturer = 0x0001  
  iProduct = 0x0002  
  iSerialNumber = 0x  
  bNumConfigurations = 0x0001

Tue Jan  1 11:54:59 CET 2019

# date ; usbconfig -d ugen0.4 dump_device_desc ; date
Tue Jan  1 14:30:19 CET 2019
ugen0.4:  at usbus0, cfg=0 md=HOST 
spd=FULL (12Mbps) pwr=ON (100mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0200
  bDeviceClass = 0x  
  bDeviceSubClass = 0x
  bDeviceProtocol = 0x
  bMaxPacketSize0 = 0x0008
  idVendor = 0x076b
  idProduct = 0x6632
  bcdDevice = 0x0103
  iManufacturer = 0x0001  
  iProduct = 0x0002  
  iSerialNumber = 0x  
  bNumConfigurations = 0x0001

Tue Jan  1 14:34:05 CET 2019

# tail -f /var/log/messages
...
Jan  1 14:34:30 c720-r342378 kernel: ugen0.4:  at usbus0 (disconnected)
Jan  1 14:34:36 c720-r342378 kernel: ugen0.4:  at usbus0


# date ; usbconfig -d ugen0.4 dump_device_desc ; date
Tue Jan  1 14:34:46 CET 2019
ugen0.4:  at usbus0, cfg=0 md=HOST 
spd=FULL (12Mbps) pwr=ON (100mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0200
  bDeviceClass = 0x  
  bDeviceSubClass = 0x
  bDeviceProtocol = 0x
  bMaxPacketSize0 = 0x0008
  idVendor = 0x076b
  idProduct = 0x6632
  bcdDevice = 0x0103
  iManufacturer = 0x0001  
  iProduct = 0x0002  
  iSerialNumber = 0x  
  bNumConfigurations = 0x0001

Tue Jan  1 14:39:13 CET 2019

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, 
Druschba
instead of Nazis, to live instead of to survive.
___
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: stop in make installworld: ld-elf.so.1: symbol lstat1@FBSD_1.5 not found

2018-12-31 Thread Matthias Apitz
On Mon, 31 Dec 2018 13:12:15 +, Dimitry Andric wrote:
> On 31 Dec 2018, at 13:08, Matthias Apitz  wrote:
>> 
>> On Mon, 31 Dec 2018 12:27:55 +0100, Matthias Apitz wrote:
>>> 
>>> Hello,
>>> 
>>> I'm updating the usual way a system from r314251 to tje 
>>> actual CURRENT r342378.
>>> The 'make installworld' failes in single user mode with:
>>> 
>>> ld-elf.so.1: /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin/rm:
>>> Undefined symbol lstat1@FBSD_1.5
>>> 
>>> What can I do?
>> 
>> As I had no other idead, I run the 'make installworld' again, 
>> now with success.
>> 
>> What does this mean?
>
> I think what may have happened was the following.
>
> The "legacy" rm which failed was likely a symlink to /bin/rm, like so:
>
> $ ls -l  /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin/rm
> lrwxr-xr-x  1 dim  dim  7 2018-12-29 16:22:12 
> /usr/obj/usr.old/src/amd64.amd64/tmp/legacy/usr/bin/rm@ -> 
> /bin/rm
>
> For some reason, /bin/rm may have been overwritten before your
> /lib/libc.so.7, which caused the "Undefined symbol" error from
> ld-elf.so.1.
>
> Alternatively, installing /lib/libc.so.7 may have failed without the
> Makefile noticing it, after which the first /bin/rm would show that same
> error.
>
> When you re-ran "make installworld", the installation of /lib/libc.so.7
> likely succeeded, and after that the symlinked commands in
> /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin which used new symbols
> started to work.
>

I still have two identical updates scheduled, based on extactly the same src 
and precompiled obj tree. I will investigate the next and file a PR.

matthias


-- 
Sent using Dekko from my Ubuntu device
http://www.unixarea.de/+49 176 38902045
___
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: stop in make installworld: ld-elf.so.1: symbol lstat1@FBSD_1.5 not found

2018-12-31 Thread Matthias Apitz
On Mon, 31 Dec 2018 12:27:55 +0100, Matthias Apitz wrote:
>
> Hello,
>
> I'm updating the usual way a system from r314251 to tje actual CURRENT 
> r342378.
> The 'make installworld' failes in single user mode with:
>
> ld-elf.so.1: /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin/rm:
> Undefined symbol lstat1@FBSD_1.5
>
> What can I do?

As I had no other idead, I run the 'make installworld' again, now with success.

What does this mean?

matthias



-- 
Sent using Dekko from my Ubuntu device
http://www.unixarea.de/+49 176 38902045
___
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"


stop in make installworld: ld-elf.so.1: symbol lstat1@FBSD_1.5 not found

2018-12-31 Thread Matthias Apitz

Hello,

I'm updating the usual way a system from r314251 the the actual CURRENT.
The 'make installworld' failes in single user mode with:

ld-elf.so.1: /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin/rm:
Undefined symbol lstat1@FBSD_1.5

What can I do?

Thanks

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
___
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: r342378 fails sometimes on boot mounting root (error 2)

2018-12-28 Thread Matthias Apitz
El día viernes, diciembre 28, 2018 a las 09:07:49a. m. -0700, Ian Lepore 
escribió:

> Try setting vfs.mountroot.timeout= in loader.conf to a value long
> enough to let the usb drive get probed reliably. The default is 3
> seconds, maybe a value like 5 or 10 would work better for you.
> 
> -- Ian

Thanks. I did so, but this does not help. When I does not work even
after 20 secs it fails to mount. After a lot of boot attempts I have the
following picture:

1. It always mounts fine when verbose message is selected.

2. It mounts fine when the line below about 'umass0:1:0: Attached to ... ' is
   printed, if it is not, the mount fails later after 20 secs waiting;
   
here is a working boot:

...
uhub1: 2 ports with 2 removable, self powered
uhub0: 13 ports with 13 removable, self powered
ugen0.2:  at usbus0
ugen0.3:  at usbus0
ugen0.4:  at usbus0
umass0 on uhub0
umass0:  
on usbus0
umass0:  SCSI over Bulk-Only; quirks = 0x8000
umass0:1:0: Attached to scbus1
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0:  ACS-2 ATA SATA 3.x device
ada0: Serial Number C196530955
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 1024bytes)
ada0: Command Queueing enabled
ada0: 244198MB (500118192 512 byte sectors)
GEOM: new disk ada0
pass0 at ahcich0 bus 0 scbus0 target 0 lun 0
pass0:  ACS-2 ATA SATA 3.x device
pass0: Serial Number C196530955
pass0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 1024bytes)
pass0: Command Queueing enabled
pass1 at umass-sim0 bus 0 scbus1 target 0 lun 0
pass1:  Fixed Direct Access SPC-4 SCSI device
pass1: Serial Number 575854314134383033483150
pass1: 40.000MB/s transfers
pass2 at umass-sim0 bus 0 scbus1 target 0 lun 1
da0 at umass-sim0 bus 0 scbus1 target 0 lun 0
da0:  Fixed Direct Access SPC-4 SCSI device
da0: Serial Number 575854314134383033483150
da0: 40.000MB/s transfers
da0: 953837MB (1953458176 512 byte sectors)
da0: quirks=0x2
pass2:  Fixed Enclosure Services SPC-4 SCSI device
pass2: Serial Number 575854314134383033483150
pass2: 40.000MB/s transfers
ses0 at umass-sim0 bus 0 scbus1 target 0 lun 1
ses0:  Fixed Enclosure Services SPC-4 SCSI device
ses0: Serial Number 575854314134383033483150
ses0: 40.000MB/s transfers
ses0: SCSI-3 ENC Device
GEOM: new disk da0
da0: Delete methods: 
WARNING: WITNESS option enabled, expect reduced performance.
Trying to mount root from ufs:/dev/gpt/extrootfs [rw,noatime]...
atrtc0: providing initial system time
start_init: trying /sbin/init
...

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
___
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"


r342378 fails sometimes on boot mounting root (error 2)

2018-12-28 Thread Matthias Apitz

Hello,

I've setup a new r342378 (December 23) for amd64 onto an external disk
with this procedure:

# grep da0 /var/log/messages
...
Dec 28 14:20:01 c720-r314251 kernel: da0 at umass-sim0 bus 0 scbus1 target 0 
lun 0
Dec 28 14:20:01 c720-r314251 kernel: da0:  Fixed 
Direct Access SPC-4 SCSI device
Dec 28 14:20:01 c720-r314251 kernel: da0: Serial Number 575854314134383033483150
Dec 28 14:20:01 c720-r314251 kernel: da0: 400.000MB/s transfers
Dec 28 14:20:01 c720-r314251 kernel: da0: 953837MB (1953458176 512 byte sectors)
Dec 28 14:20:01 c720-r314251 kernel: da0: quirks=0x2


# gpart destroy -F da0
da0 destroyed
# gpart create -s gpt da0
da0 created
# gpart add -t freebsd-boot -s 512k -a4k -l extboot da0
da0p1 added
# gpart bootcode -b /boot/pmbr -p /boot/gptboot -i1 da0
partcode written to da0p1
bootcode written to da0
# gpart add -t freebsd-ufs -l  extrootfs -b 1m -s 256g da0
da0p2 added
# gpart add -t freebsd-swap -l extswap -a 1m -s 2g da0
da0p3 added
# gpart add -t freebsd-ufs -l  extbackupfs -a 1m da0
da0p4 added

# newfs -U /dev/gpt/extrootfs
# newfs -U /dev/gpt/extbackupfs

# gpart set -a active da0
active set on da0
# gpart show -l da0
=>40  1953458096  da0  GPT  (931G)
  4010241  extboot  (512K)
1064 984   - free -  (492K)
2048   5368709122  extrootfs  (256G)
   536872960 41943043  extswap  (2.0G)
   541067264  14123888644  extbackupfs  (673G)
  19534561282008   - free -  (1.0M)


# mount /dev/gpt/extrootfs /mnt

# cd /usr/src
# make installworld  DESTDIR=/mnt
# make installkernel DESTDIR=/mnt
# make distrib-dirs  DESTDIR=/mnt
# make distribution  DESTDIR=/mnt

# cd ~guru/C720

# cp -p rc.conf /mnt/etc
# cp -p c720.kbd/mnt/etc
# cp -p sysctl.conf /mnt/etc
# cp -p loader.conf /mnt/boot/
# cp -p device.hints/mnt/boot/

# cat > /mnt/etc/fstab  

Re: unknown (doubled?) poudriere jail below /usr/obj/usr/local/...

2018-12-26 Thread Matthias Apitz
El día Wednesday, December 26, 2018 a las 09:49:20AM +0100, Matthias Apitz 
escribió:

> 
> Hello,
> 
> I've update on December 23 an amd64 system to r342378 and
> created a new ZFS jail and ports within poudriere with:
> 
> # poudriere jail  -c -j freebsd-r342378 -m svn+http -v head@r342378
> # poudriere ports -c -p ports-20181223  -m svn -U svn://svn.freebsd.org/ports/
> 
> The relevant values from poudriere.conf are:
> 
> 

I did (just for test) a 2nd jail creation as:

# poudriere jail  -c -j freebsd-r342378test -m svn+http -v head@r342378

this checks out the source tree to 
/usr/local/poudriere/jails/freebsd-r342378test/usr/src

and compiles it to /usr/obj/usr/local/poudriere/jails/freebsd-r342378test/usr 
...
one can also see this in the run of the compiler, here an example:

...
c++  -O2 -pipe
-I/usr/obj/usr/local/poudriere/jails/freebsd-r342378test/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libllvm
-I/usr/local/poudriere/jails/freebsd-r342378test/usr/src/lib/clang/include
-I/usr/local/poudriere/jails/freebsd-r342378test/usr/src/contrib/llvm/include
-DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS
-DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd13.0\"
-DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd13.0\"
-DDEFAULT_SYSROOT=\"/usr/obj/usr/local/poudriere/jails/freebsd-r342378test/usr/src/amd64.amd64/tmp\"
-DLLVM_TARGET_ENABLE_X86
-DLLVM_NATIVE_ASMPARSER=LLVMInitializeX86AsmParser
-DLLVM_NATIVE_ASMPRINTER=LLVMInitializeX86AsmPrinter
-DLLVM_NATIVE_DISASSEMBLER=LLVMInitializeX86Disassembler
-DLLVM_NATIVE_TARGET=LLVMInitializeX86Target
-DLLVM_NATIVE_TARGETINFO=LLVMInitializeX86TargetInfo
-DLLVM_NATIVE_TARGETMC=LLVMInitializeX86TargetMC -ffunction-sections
-fdata-sections -gline-tables-only -MD -MF.depend.X86FoldTablesEmitter.o
-MTX86FoldTablesEmitter.o -Qunused-arguments
-I/usr/obj/usr/local/poudriere/jails/freebsd-r342378test/usr/src/amd64.amd64/tmp/legacy/usr/include
-std=c++11 -fno-exceptions -fno-rtti -stdlib=libc++
-Wno-c++11-extensions  -c
/usr/local/poudriere/jails/freebsd-r342378test/usr/src/contrib/llvm/utils/TableGen/X86FoldTablesEmitter.cpp
-o X86FoldTablesEmitter.o
...

Is this pollution of /usr/obj with the poudriere jail intention? And can
this be removed later?

For my original jail 'freebsd-r342378' I moved away '/usr/obj/usr/local'
to '/local-UNKNOWN' and the jail is still working fine (compiled fice
hours www/chromium). 

Please, poudriere folks help me to understand this? Is this new with
some version (I have not found anything in /usr/ports/UPDATING or in the
man page). It was not this way in version r314251 (in March 2017).

Thanks

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, 
Druschba
instead of Nazis, to live instead of to survive.


signature.asc
Description: PGP signature


unknown (doubled?) poudriere jail below /usr/obj/usr/local/...

2018-12-26 Thread Matthias Apitz

Hello,

I've update on December 23 an amd64 system to r342378 and
created a new ZFS jail and ports within poudriere with:

# poudriere jail  -c -j freebsd-r342378 -m svn+http -v head@r342378
# poudriere ports -c -p ports-20181223  -m svn -U svn://svn.freebsd.org/ports/

The relevant values from poudriere.conf are:

ZPOOL=poudriere
#NO_ZFS=yes
ZROOTFS=/poudriere
BASEFS=/usr/local/poudriere
POUDRIERE_DATA=${BASEFS}/data



Since then I compiled some 1800 ports with:

# poudriere bulk -f /usr/local/etc/poudriere-list -J 4 -j freebsd-r342378 -p 
ports-20181223

All went fine.

While checking something, I now see the poudriere jail also below 
/usr/obj/usr/local:

[root@jet ~]# ls -li /usr/local/poudriere/jails/ 
/usr/obj/usr/local/poudriere/jails/
/usr/local/poudriere/jails/:
total 3
4 drwxr-xr-x  17 root  wheel  21 Mar  4  2017 freebsd-r314251
4 drwxr-xr-x  18 root  wheel  22 Dec 23 21:30 freebsd-r342378

/usr/obj/usr/local/poudriere/jails/:
total 4
31300766 drwxrwxr-x  3 root  wheel  512 Dec 23 19:22 freebsd-r342378

The mounts are:

[root@jet ~]# mount
/dev/da0p2 on / (ufs, local, journaled soft-updates)
devfs on /dev (devfs, local, multilabel)
poudriere on /poudriere (zfs, local, nfsv4acls)
poudriere/poudriere on /poudriere/poudriere (zfs, local, nfsv4acls)
poudriere/poudriere/jails on /poudriere/poudriere/jails (zfs, local, nfsv4acls)
poudriere/poudriere/ports on /poudriere/poudriere/ports (zfs, local, nfsv4acls)
poudriere/mydata on /usr/home/guru/zdata (zfs, local, nfsv4acls)
poudriere/mydata/r338641 on /usr/home/guru/zdata/r338641 (zfs, local, nfsv4acls)
poudriere/poudriere/jails/freebsd-r314251 on 
/usr/local/poudriere/jails/freebsd-r314251 (zfs, local, noatime, nfsv4acls)
poudriere/poudriere/jails/freebsd-r342378 on 
/usr/local/poudriere/jails/freebsd-r342378 (zfs, local, noatime, nfsv4acls)
poudriere/poudriere/ports/ports-20170304 on 
/usr/local/poudriere/ports/ports-20170304 (zfs, local, noatime, nfsv4acls)
poudriere/poudriere/ports/ports-20181223 on 
/usr/local/poudriere/ports/ports-20181223 (zfs, local, noatime, nfsv4acls)

What does this structure below '/usr/obj/usr/local/poudriere/jails/'
mean? Can I remove this?

Thanks for some light on this.

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, 
Druschba
instead of Nazis, to live instead of to survive.


signature.asc
Description: PGP signature


Re: kdelibs-kde4 is marked as broken on FreeBSD 13.0: incompatible with base SSL ...

2018-12-25 Thread Matthias Apitz
El día lunes, diciembre 24, 2018 a las 01:16:40p. m. +0100, Adriaan de Groot 
escribió:

> On Monday, 24 December 2018 11:24:59 CET Jan Beich wrote:
> > g...@unixarea.de writes:
> > > I know that KDE4 will be removed from ports by the end of the year,
> > > that's why I wanted to update my CURRENT and ports right now before
> > > this. I now find that one of the fundamental ports (x11/kdelibs-kde4) is
> > > marked as broken...
> > > 
> > > Is there a fix for this (for example using SSL from ports and not from
> > > base). The alternative would be reset my poudriere oven to a 19 of
> > > September (my last build with KDE4).
> > 
> > Try adding DEFAULT_VERSIONS+=ssl=openssl to make.conf(5) and commenting
> > out BROKEN_FreeBSD_13 in kdelibs-kde4/Makefile.
> 
> What Jan said will *probably* work. We (kde@) do not have the person-hours to 
> chase this. You'll want a ports tree from last week, since we've been 
> updating 
> KDE4-era ports to their current releases recently, if you're particularly 
> attached to the unmaintained stuff.
> 
> [ade]

Thanks to you both (Jan and Adriaan) for your help and your work in
general!

It's a pity that KDE4 is unmaintained (upstream and in FreeBSD) because
it does fine for me and many others for many years. From time to time I have to
use KDE5 at work on SUSE Linux workstations and it's rather strange to
use this as a C(K)ommon Desktop Environment, to be honestly. That's why
I see a lot of mails and PR, for example
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233182
expressing the same.

Anyway, I will try to get it compiled based on your hint, and if not either 
return to
a September version or switch to KDE5.

Thanks again.

matthias


-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, 
Druschba
instead of Nazis, to live instead of to survive.


signature.asc
Description: PGP signature


Re: debugging a run of poudriere-bulk

2018-10-05 Thread Matthias Apitz
El día Thursday, October 04, 2018 a las 01:14:55PM +0930, Shane Ambler escribió:

> > How can I enter the jail interactively in the moment after the crash to 
> > rerun and
> > debug pkg-static?
> 
> Using
> 
> poudriere testport -j  -p  -i -o 
> 
> will drop you into the jail after the build stops, you then rerun make
> manually, check build logs... Logging out will then continue on and
> clean up the jail. You can also use -I instead of -i and it leaves the
> jail in place so you can manually connect to and stop the jail.
> 
> Note that poudriere uses a clean jail with only deps listed for the
> port, you can add extra BUILD_DEPENDS to get extra ports (gdb valgrind)
> installed with the test build.

Thanks! One should read man pages completely in advance and not only the
part of 'poudriere bulk ...'.

I did so and in nthis case the crash occurs *after* the package is
complete:


...
> Checking for pkg-plist issues (check-plist)
===> Parsing plist
===> Checking for items in STAGEDIR missing from pkg-plist
===> Checking for items in pkg-plist which are not in STAGEDIR
===> No pkg-plist issues found (check-plist)
=>> Checking for staging violations... done
===
===>  Building package for kde-workspace-kde4-4.11.22_26
file sizes/checksums  [2126]: .. done
packing files [2126]: .. done
packing directories  [0]: . done
===
=>> Recording filesystem state for preinst... done
===
===>  Installing for kde-workspace-kde4-4.11.22_26
===>  Checking if kde-workspace-kde4 already installed
===>   Registering installation for kde-workspace-kde4-4.11.22_26
Child process pid=75639 terminated abnormally: Segmentation faul
*** Error code 139

Stop.
make: stopped in /usr/ports/x11/kde-workspace-kde4
===
[00:13:29] Installing packages
[00:13:29] Installing run-depends for x11/kde-workspace-kde4 | 
kde-workspace-kde4-4.11.22_26


# ls -l 
/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/pkg/kde-workspace-kde4-4.11.22_26.txz
-rw-r--r--  1 nobody  wheel  18338720 Oct  4 14:02 
/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/pkg/kde-workspace-kde4-4.11.22_26.txz

Poudriere installs the package 'pkg' into the jail to could make use of
'pkg-static' (and other tools). Maybe it would be an idea to create
outside a special version of this package which have a special version
of 'pkg-static' in this, for example a shellsript with the name
pkg-static which is something like:

#!/bin/sh
echo $0 $* > /tmp/pkg-static-args.$$
truss -o /tmp/pkg-static.$$ /usr/local/sbin/pkgstatic.exec $*

to get more information about the crash.

Other ideas?

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, 
Druschba
instead of Nazis, to live instead of to survive.
___
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: debugging a run of poudriere-bulk

2018-10-03 Thread Matthias Apitz
El día miércoles, octubre 03, 2018 a las 11:06:55p. m. +0200, Tobias C. Berner 
escribió:

> Moin moin
> 
> Unfortunately it is very hard to help here when not being able to reproduce
> the issue :/
> Have you tried wiping all the packages in poudriere's repo? -- i.e. -c --
> maybe you're pkg package is just hosed.

Tobias,

The problem *is* reproducible, even in the build clusters of freebsd.org
(see pkg-fallout messages). It is only (until now) not debug-able.

    matthias


-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
October 3: Day of German Unity? No! Day of taking over the GDR.
3. Oktober: Tag der Deutschen Einheit? Nein! DDR-Anschlusstag.


signature.asc
Description: PGP signature


Re: debugging a run of poudriere-bulk

2018-10-03 Thread Matthias Apitz

I added the following lines to /usr/local/share/poudriere/bulk.sh to get
the env vars into the environment of pkg(8):

export DEBUG_LEVEL=4
export DEBUG_SCRIPTS=TRUE
export DEVELOPER_MODE=TRUE
export PKG_CREATE_VERBOSE=TRUE

With these the port builds fine:

# tail -f 
/usr/local/poudriere/data/logs/bulk/freebsd-r338641-ports-20180920/2018-10-03_22h03m46s/logs/kde-workspace-kde4-4.11.22_26.log
...

DBG(1)[94432]> PkgConfig: loading repositories in /etc/pkg/
DBG(1)[94432]> PKgConfig: loading /etc/pkg//FreeBSD.conf
DBG(1)[94432]> PkgConfig: parsing key 'FreeBSD'
DBG(1)[94432]> PkgConfig: parsing repository object FreeBSD
DBG(1)[94432]> PkgConfig: loading repositories in /usr/local/etc/pkg/repos/
DBG(1)[94432]> Creating package from stage directory: 
'/wrkdirs/usr/ports/x11/kde-workspace-kde4/wor
k/stage'
DBG(1)[94432]> Parsing manifest from '+MANIFEST'
DBG(3)[94432]> Manifest: found key: 'name'

...

DBG(2)[94432]> Packing file 
'/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/share/wallpapers/stripes.png.desktop'
DBG(2)[94432]> Packing file 
'/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/share/xsessions/kde4.desktop'
DBG(2)[94432]> Packing file 
'/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/etc/rc.d/kdm4'
packing files [2126]... done
packing directories  [0]: . done
===
=>> Cleaning up wrkdir
===>  Cleaning for kde-workspace-kde4-4.11.22_26
build of x11/kde-workspace-kde4 | kde-workspace-kde4-4.11.22_26 ended at Wed 
Oct  3 22:15:54 CEST 2018
build time: 00:11:21

i.e. the pkg-static does not crash.

And now?

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
October 3: Day of German Unity? No! Day of taking over the GDR.
3. Oktober: Tag der Deutschen Einheit? Nein! DDR-Anschlusstag.


signature.asc
Description: PGP signature


Re: debugging a run of poudriere-bulk

2018-10-03 Thread Matthias Apitz
El día miércoles, octubre 03, 2018 a las 01:41:14p. m. +0200, Matthias Apitz 
escribió:

> 
> Hello,
> 
> 
> I'm trying to nail down PR 231532 of a port which fails to build in
> poudriere. In the last phase of the ports build, while creating the pkg
> of the built port with pkg-static, this crashes:

When I do run pudriere bulk with -vv options, it says only:

[00:02:40] [01] [00:01:51] Status   x11/kde-workspace-kde4 | 
kde-workspace-kde4-4.11.22_26: build
[00:10:41] [01] [00:09:52] Status   x11/kde-workspace-kde4 | 
kde-workspace-kde4-4.11.22_26: run-depends
[00:10:46] [01] [00:09:57] Status   x11/kde-workspace-kde4 | 
kde-workspace-kde4-4.11.22_26: stage
[00:11:42] [01] [00:10:53] Status   x11/kde-workspace-kde4 | 
kde-workspace-kde4-4.11.22_26: package
[00:11:46] [01] [00:10:57] Finished x11/kde-workspace-kde4 | 
kde-workspace-kde4-4.11.22_26: Failed: package
[00:11:46] Stopping 1 builders

    matthias


-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
October 3: Day of German Unity? No! Day of taking over the GDR.
3. Oktober: Tag der Deutschen Einheit? Nein! DDR-Anschlusstag.


signature.asc
Description: PGP signature


debugging a run of poudriere-bulk

2018-10-03 Thread Matthias Apitz

Hello,


I'm trying to nail down PR 231532 of a port which fails to build in
poudriere. In the last phase of the ports build, while creating the pkg
of the built port with pkg-static, this crashes:

# tail 
/usr/local/poudriere/data/logs/bulk/freebsd-r338641-ports-20180920/2018-10-03_11h32m17s/logs/kde-workspace-kde4-4.11.22_26.log
Child process pid=85086 terminated abnormally: Segmentation fault
*** Error code 1

Stop.
make: stopped in /usr/ports/x11/kde-workspace-kde4
=>> Cleaning up wrkdir

# grep 85086 /var/log/messages
Oct  3 11:44:01 jet kernel: pid 85086 (pkg-static), uid 65534: exited on signal 
11


How can I enter the jail interactively in the moment after the crash to rerun 
and
debug pkg-static?

When I run 'poudriere bulk -i ...' the port builds fine:

# poudriere bulk -i -J 1 -j freebsd-r338641 -p ports-20180920 
x11/kde-workspace-kde4


# cd /usr/ports/x11/kde-workspace-kde4
# make package
gmake[1]: Leaving directory 
'/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/.build'
install -l rs 
/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/bin/startkde 
/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/bin/startkde4
/bin/mkdir -p 
/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/share/xsessions
install  -m 0644 /usr/ports/x11/kde-workspace-kde4/files/kde4.desktop 
/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/share/xsessions
> Compressing man pages (compress-man)
===> Staging rc.d startup script(s)
===>  Building package for kde-workspace-kde4-4.11.22_26
cp: /packages/All/kde-workspace-kde4-4.11.22_26.txz: Read-only file system
*** Error code 1

Stop.
make: stopped in /usr/ports/x11/kde-workspace-kde4

# cd /usr/ports/x11/kde-workspace-kde4
# ls -l
total 42
-rw-r--r--  1 root  wheel5480 Sep 20 05:16 Makefile
-rw-r--r--  1 root  wheel 225 Sep 20 05:16 distinfo
drwxr-xr-x  2 root  wheel  30 Sep 20 05:16 files
-rw-r--r--  1 root  wheel 219 Sep 20 05:16 pkg-descr
-rw-r--r--  1 root  wheel  100336 Sep 20 05:16 pkg-plist
# ls -la /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/pkg
total 17921
drwxr-xr-x  2 root  wheel64 Oct  3 09:13 .
drwxr-xr-x  7 root  wheel   960 Oct  3 09:13 ..
-rw-r--r--  1 root  wheel  18346688 Oct  3 09:13 
kde-workspace-kde4-4.11.22_26.txz

# scp -p 
/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/pkg/kde-workspace-kde4-4.11.22_26.txz
 guru@192.168.2.35:/tmp

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
13. August 2018: Ich würde gern einen AUSREISEANTRAG stellen.
August 13, 2018: I'd like to ask for an exit permit of this country.


signature.asc
Description: PGP signature


Re: PR id=231810

2018-09-30 Thread Matthias Apitz
El día Sunday, September 30, 2018 a las 08:12:17PM +1000, Kubilay Kocak 
escribió:

> On 30/09/2018 5:52 pm, Matthias Apitz wrote:
> > 
> > Hello,
> > 
> > Can some kind soul please modify this PR to reflect the Version and the
> > affected people:
> > 
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231810
> > 
> > Thanks
> > 
> > matthias
> > 
> 
> Hi Matthias,
> 
> I've updated the Severity, but the Version is better left at the lowest
> (earliest) reported/confirmed version, to ensure it gets merged back to
> the relevant stable branch.

Hello Kubilay,

At work we use Atlassian's JIRA as bugtracking system. This allows to set
multiple versions affected by a single issue. Doesn't bugzilla allow
this?

Thanks anyway for changing the Severity. If someone needs me for some
test to nail down this, I have a system for this.

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/   
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
13. August 2018: Manchmal möchte ich nun einen AUSREISEANTRAG stellen.
August 13, 2018: Sometimes I'd like to ask for an exit permission now.
___
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"


PR id=231810

2018-09-30 Thread Matthias Apitz

Hello,

Can some kind soul please modify this PR to reflect the Version and the
affected people:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231810

Thanks

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


signature.asc
Description: PGP signature


mkimg(1) creates a file in TMPDIR until no space left

2018-09-29 Thread Matthias Apitz

Hello,

I'm using a copy of src/release/amd64/make-memstick.sh to build from a
complete root in /usr/local/r338641/root.r338641 (result of make
installworld and installkernel to this dir) for testing purpose a memstick
image and write this with dd(1) to an USB key of ~32 GByte. I'm using a
copy of this script because I want to define the size of the UFS in the
image to have there enough free space to install later after boot as
well packages to test them.

The modification is only setting '-M 50331648b -m 50331648b' for the file
system created with mkfs(8). Here is what is running exactly:

# TMPDIR=/usr/tmp export TMPDIR
# ./make-memstick.sh /usr/local/r338641/root.r338641 
/usr/local/r338641/memstick.im
+ makefs -B little -M 50331648b -m 50331648b -o 'label=FreeBSD_Install' -o 
'version=2' /usr/local/r338641/memstick.im.part /usr/local/r338641/root.r338641
Calculated size of `/usr/local/r338641/memstick.im.part': 25769803776 bytes, 
24530 inodes
Extent size set to 32768
/usr/local/r338641/memstick.im.part: 24576.0MB (50331648 sectors) block size 
32768, fragment size 4096
using 28 cylinder groups of 901.44MB, 28846 blks, 1024 inodes.
super-block backups (for fsck -b #) at:
  192,  1846336,  3692480,  5538624,  7384768,  9230912, 11077056,
 12923200, 14769344, 16615488, 18461632, 20307776, 22153920, 2464,
 25846208, 27692352, 29538496, 31384640, 33230784, 35076928, 36923072,
 38769216, 40615360, 42461504, 44307648, 46153792, 4736, 49846080,
Populating `/usr/local/r338641/memstick.im.part'
Image `/usr/local/r338641/memstick.im.part' complete
+ rm /usr/local/r338641/root.r338641/etc/fstab
+ rm /usr/local/r338641/root.r338641/etc/rc.conf.local
+ mkimg -C 28G -s mbr -b /usr/local/r338641/root.r338641/boot/mbr -p 
'efi:=/usr/local/r338641/root.r338641/boot/boot1.efifat' -p 'freebsd:-mkimg -C 
28G -s bsd -b /usr/local/r338641/root.r338641/boot/boot -p 
freebsd-ufs:=/usr/local/r338641/memstick.im.part' -a 2 -o 
/usr/local/r338641/memstick.im
...


While the cascade of mkimg(1) is running a *big* temp file is created,
which at the end eats up all memory of the disk:

# ls -lh /usr/local/r338641 /usr/tmp
/usr/local/r338641:
total 25172008
-rwxr-xr-x   1 root  wheel   1.3K Sep 29 16:41 make-memstick.sh
-rw-r--r--   1 root  wheel 0B Sep 29 16:50 memstick.im
-rw-r--r--   1 root  wheel24G Sep 29 16:50 memstick.im.part
drwxr-xr-x  18 root  wheel   512B Sep 24 07:11 root.r338641

/usr/tmp:
total 11307168
-rw---  1 root  wheel   456G Sep 29 17:01 mkimg-LmntlL<<< 456G 
!!!
-rw---  1 root  wheel 0B Sep 29 16:50 mkimg-yfU8Lr

/: write failed, filesystem is full

/: write failed, filesystem is full

But the 'memstick.im' is created fine at the end:

# ls -lh /usr/local/r338641 /usr/tmp
/usr/local/r338641:
total 2591752
-rwxr-xr-x   1 root  wheel   1.3K Sep 29 16:41 make-memstick.sh
-rw-r--r--   1 root  wheel24G Sep 29 17:22 memstick.im
drwxr-xr-x  18 root  wheel   512B Sep 24 07:11 root.r338641

/usr/tmp:
total 0

And the UBS stick produced from 'memstick.im' with dd(1) boots fine and the root
file system has around 20 GB free space.

Why it is mkimg(1) creating such a big temp. file?

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
___
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: r338641 && /dev/cyapa0: moused does not show pointer on console

2018-09-24 Thread Matthias Apitz
El día Monday, September 24, 2018 a las 09:01:34PM +0200, Michael Gmelin 
escribió:

> >> On 24/09/2018 13:21, Matthias Apitz wrote:
> >> Re/ i915kms, I have to load it with kldload by hand. If I load it via
> >> loader.conf, the cyapa devices (both) say 'Unable to bring the device
> >> out of bootstrap'.
> > 
> > That's probably because you use device hints to configure cyapa, but i2c bus
> > numbers are different depending on whether the kms driver is loaded or not
> > (because it also creates i2c buses).
> > 
> > Try to remove the hints and to use chromebook_platform(4) instead.

Thanks, I will test

chromebook_platform_load="YES"

> Also, I think the preferred way to load i915kms is to use kld_list (might be 
> unrelated, but still).
> 
> pkg install drm-next-kmod
> sysrc kld_list="/boot/modules/i915kms.ko"

Thanks too. On my laptop in production I do use a handmade script 
/usr/local/etc/rc.d/loadi915kms to load the module at late time.

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/   
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
___
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: r338641 && /dev/cyapa0: moused does not show pointer on console

2018-09-24 Thread Matthias Apitz
El día Monday, September 24, 2018 a las 12:46:17PM +0300, Michael Gmelin 
escribió:

> > What could be wrong?
> 
> Do you by any chance use vt(4) in vga textmode (hw.vga.textmode=1)?
> 
> vt doesn’t support hardware mouse cursors, so no cursor in text mode (see 
> https://wiki.freebsd.org/Newcons)
> 

Thanks. When I remove hw.vga.textmode=1 the mouse pointer comes up and
works.

Re/ i915kms, I have to load it with kldload by hand. If I load it via
loader.conf, the cyapa devices (both) say 'Unable to bring the device
out of bootstrap'.

    matthias


-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/   
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
___
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: r338641 && /dev/cyapa0: moused does not show pointer on console

2018-09-24 Thread Matthias Apitz
El día Monday, September 24, 2018 a las 10:31:38AM +0200, Matthias Apitz 
escribió:

> 
> Hello,
> 
> I've booted a fresh r338641 from an USB key on my Acer C720, and have
> the required modules loaded at boot (cyapa and ig4) and the values for cyapa 
> in
> /boot/device.hints, as I do use them in r314251. The moused is running as
> 
> /usr/sbin/moused -p /dev/cyapa0 -t ps/2
> 
> but no mouse pointer is written on the console. If I do
> 
> # cat /dev/cyapa0
> 
> on TP movements, bytes can be read by cat(1). And trussing the PID of
> the moused shows too that it is reading bytes.
> 
> What could be wrong?

additional information: when I do load *after* boot

# kldload i915kms

the mouse pointer appears and can be moved.

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/   
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
___
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"


r338641 && /dev/cyapa0: moused does not show pointer on console

2018-09-24 Thread Matthias Apitz

Hello,

I've booted a fresh r338641 from an USB key on my Acer C720, and have
the required modules loaded at boot (cyapa and ig4) and the values for cyapa in
/boot/device.hints, as I do use them in r314251. The moused is running as

/usr/sbin/moused -p /dev/cyapa0 -t ps/2

but no mouse pointer is written on the console. If I do

# cat /dev/cyapa0

on TP movements, bytes can be read by cat(1). And trussing the PID of
the moused shows too that it is reading bytes.

What could be wrong?

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/   
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
___
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: CURRENT r338641 with poudriere-devel: seg fault on building x11/kde-workspace-kde4

2018-09-21 Thread Matthias Apitz
El día Friday, September 21, 2018 a las 11:17:59AM +0200, Matthias Apitz 
escribió:

> ===
> ===>   kde-workspace-kde4-4.11.22_26 depends on file: /usr/local/sbin/pkg - 
> not found
> ===>   Installing existing package /packages/All/pkg-1.10.5_3.txz
> [freebsd-r338641-ports-20180920-job-03] Installing pkg-1.10.5_3...
> [freebsd-r338641-ports-20180920-job-03] Extracting pkg-1.10.5_3: .. 
> done
> 
> I will remove this pkg /packages/All/pkg-1.10.5_3.txz again and will
> poudriere ask to build ports-mgmt/pkg-devel instead of this, because
> this is already on level 1.10.99.

I found no way that poudriere uses ports-mgmt/pkg-devel, it always
compiles again ports-mgmt/pkg before kde-workspace-kde4-4.11.22_26,
which crashes :-(

Any hints?

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/   
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
___
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: CURRENT r338641 with poudriere-devel: seg fault on building x11/kde-workspace-kde4

2018-09-21 Thread Matthias Apitz
El día Friday, September 21, 2018 a las 10:08:57AM +0200, Matthias Apitz 
escribió:

> I filed a PR re/ ports:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231532
> 
> but I think the culprit is the base system because the component which
> segfaults is 'pkg-static':
> 
> ...
> ===
> ===>  Building package for kde-workspace-kde4-4.11.22_26
> Child process pid=67229 terminated abnormally: Segmentation fault
> *** Error code 1
> 
> /var/log/messages:
> 
> Sep 21 09:19:51 jet kernel: pid 67229 (pkg-static), uid 65534: exited on 
> signal 11
> 
> As this is running in a poudriere jail, how could I get a core file of
> this?

This is ofc a bit wrong because poudriere is installing the port to have
pkg:

===
===>   kde-workspace-kde4-4.11.22_26 depends on file: /usr/local/sbin/pkg - not 
found
===>   Installing existing package /packages/All/pkg-1.10.5_3.txz
[freebsd-r338641-ports-20180920-job-03] Installing pkg-1.10.5_3...
[freebsd-r338641-ports-20180920-job-03] Extracting pkg-1.10.5_3: .. done

I will remove this pkg /packages/All/pkg-1.10.5_3.txz again and will
poudriere ask to build ports-mgmt/pkg-devel instead of this, because
this is already on level 1.10.99.

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/   
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
___
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: CURRENT r338641 with poudriere-devel: seg fault on building x11/kde-workspace-kde4

2018-09-21 Thread Matthias Apitz
El día Friday, September 21, 2018 a las 06:54:25AM +0200, Matthias Apitz 
escribió:

> 
> Hello,
> 
> I have here a reproducible Segmentation fault in staging phase of the
> port x11/kde-workspace-kde4; the full log file is here:
> http://www.unixarea.de/kde-workspace-kde4-4.11.22_26.log
> 
> The first few lines and the end of the log are below; any comments or
> hints how to nail this down? Thanks

I filed a PR re/ ports:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231532

but I think the culprit is the base system because the component which
segfaults is 'pkg-static':

...
===
===>  Building package for kde-workspace-kde4-4.11.22_26
Child process pid=67229 terminated abnormally: Segmentation fault
*** Error code 1

/var/log/messages:

Sep 21 09:19:51 jet kernel: pid 67229 (pkg-static), uid 65534: exited on signal 
11

As this is running in a poudriere jail, how could I get a core file of
this?

    matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/   
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
___
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"


CURRENT r338641 with poudriere-devel: seg fault on building x11/kde-workspace-kde4

2018-09-20 Thread Matthias Apitz

Hello,

I have here a reproducible Segmentation fault in staging phase of the
port x11/kde-workspace-kde4; the full log file is here:
http://www.unixarea.de/kde-workspace-kde4-4.11.22_26.log

The first few lines and the end of the log are below; any comments or
hints how to nail this down? Thanks

matthias


=>> Building x11/kde-workspace-kde4
build started at Fri Sep 21 05:23:49 CEST 2018
port directory: /usr/ports/x11/kde-workspace-kde4
package name: kde-workspace-kde4-4.11.22_26
building for: FreeBSD freebsd-r338641-ports-20180920-job-03 12.0-ALPHA5 FreeBSD 
12.0-ALPHA5 1200084 amd64
maintained by: k...@freebsd.org
Makefile ident:  $FreeBSD: head/x11/kde-workspace-kde4/Makefile 479538 
2018-09-11 18:34:27Z zeising $
Poudriere version: 3.2.99.20180601
Host OSVERSION: 1200084
Jail OSVERSION: 1200084
Job Id: 03

---Begin Environment---
SHELL=/bin/csh
OSVERSION=1200084
UNAME_v=FreeBSD 12.0-ALPHA5 1200084
UNAME_r=12.0-ALPHA5
BLOCKSIZE=K
MAIL=/var/mail/root
STATUS=1
HOME=/root
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin
LOCALBASE=/usr/local
USER=root
LIBEXECPREFIX=/usr/local/libexec/poudriere
POUDRIERE_VERSION=3.2.99.20180601
MASTERMNT=/usr/local/poudriere/data/.m/freebsd-r338641-ports-20180920/ref
POUDRIERE_BUILD_TYPE=bulk
PACKAGE_BUILDING=yes
SAVED_TERM=screen
GID=0
UID=0
PWD=/usr/local/poudriere/data/.m/freebsd-r338641-ports-20180920/ref/.p/pool
P_PORTS_FEATURES=FLAVORS SELECTED_OPTIONS
MASTERNAME=freebsd-r338641-ports-20180920
SCRIPTPREFIX=/usr/local/share/poudriere
OLDPWD=/usr/local/poudriere/data/.m/freebsd-r338641-ports-20180920/ref/.p
SCRIPTPATH=/usr/local/share/poudriere/bulk.sh
POUDRIEREPATH=/usr/local/bin/poudriere
---End Environment---

---Begin Poudriere Port Flags/Env---
PORT_FLAGS=
PKGENV=
FLAVOR=
DEPENDS_ARGS=
MAKE_ARGS=
---End Poudriere Port Flags/Env---

---Begin OPTIONS List---
===> The following configuration options are available for 
kde-workspace-kde4-4.11.22_26:
 GLES=on: OpenGL ES 2.0 support in kwin and kinfocenter
 GPS=on: GPS geolocation via gpsd
 KACTIVITY=on: Activity Manager daemon
 UPOWER=on: Power management via UPower
 WALLPAPERS=on: Install official KDE wallpapers
> Multimedia support via Phonon
 GSTREAMER=off: Multimedia via Phonon-GStreamer
 VLC=on: Multimedia via Phonon-VLC
> Options available for the group PLASMA
 PYTHON=off: Python plasmoids support
 RUBY=off: Ruby plasmoids support
===> Use 'make config' to modify these settings
---End OPTIONS List---

--MAINTAINER--
k...@freebsd.org
--End MAINTAINER--

--CONFIGURE_ARGS--

--End CONFIGURE_ARGS--

...


-- Installing: 
/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/share/apps/kstyle/themes/qtplastique.themerc
-- Installing: 
/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/share/apps/kstyle/themes/qtwindows.themerc
-- Installing: 
/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/share/apps/kstyle/themes/qtgtk.themerc
gmake[1]: Leaving directory 
'/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/.build'
install -l rs 
/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/bin/startkde 
/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/bin/startkde4
/bin/mkdir -p 
/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/share/xsessions
install  -m 0644 /usr/ports/x11/kde-workspace-kde4/files/kde4.desktop 
/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/share/xsessions
> Compressing man pages (compress-man)
===> Staging rc.d startup script(s)
===
===
===>  Building package for kde-workspace-kde4-4.11.22_26
Child process pid=81309 terminated abnormally: Segmentation fault
*** Error code 1

Stop.
make: stopped in /usr/ports/x11/kde-workspace-kde4
=>> Cleaning up wrkdir
===>  Cleaning for kde-workspace-kde4-4.11.22_26
build of x11/kde-workspace-kde4 | kde-workspace-kde4-4.11.22_26 ended at Fri 
Sep 21 05:40:40 CEST 2018
build time: 00:16:51
!!! build failure encountered !!!


-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


signature.asc
Description: PGP signature


updating my pordriere oven to latest CURRENT

2018-09-17 Thread Matthias Apitz

Hello,


I'm short before updating my poudriere oven, a Dell PowerEdge r210, from
r318593 to r338641. I have there a ZFS in use for poudriere, created
with:

# zpool create poudriere /dev/da1

and set in /usr/local/etc/poudriere.conf:

  ZPOOL=poudriere
ZROOTFS=/poudriere

# zpool list
NAMESIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
poudriere   278G  3.90G   274G -13% 1%  1.00x  ONLINE  -

# mount
/dev/da0p2 on / (ufs, local, journaled soft-updates)
devfs on /dev (devfs, local, multilabel)
poudriere on /poudriere (zfs, local, nfsv4acls)
poudriere/poudriere on /poudriere/poudriere (zfs, local, nfsv4acls)
poudriere/poudriere/jails on /poudriere/poudriere/jails (zfs, local, nfsv4acls)
...


Before running 'make installkernel' ... and later updating the poudriere
tool itself from ports too, I wanted to ask if I have to take care about
anything before. I've read src/UPDATING between the above mentioned versions and
can't see anything, i.e. the zpool should be fine after the update too.

Any comments on this? Thanks


matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/   
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
___
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: TCP server app performance

2018-08-12 Thread Matthias Apitz
El día domingo, agosto 12, 2018 a las 09:32:28p. m. +0200, Michio Honda 
escribió:

> Hi Rozhuk,
> 
> I only use a single CPU core and thread, so SO_REUSEPORT_LB has no 
> effect. Also, I already accept() in loop until getting error, but this 
> is not a point as I use persistent TCP connections...
> 
> Cheers,
> - Michio

Hi Michio,

Don't top post, please.

    matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
13. August 2018: Ich würde gern einen AUSREISEANTRAG stellen.
August 13, 2018: I'd like to ask for an exit permit of this country.


signature.asc
Description: PGP signature


Re: Elantech Touchpad Woes - Support for Elantech touchpads over i2c/SMBus still possibly missing

2018-06-02 Thread Matthias Apitz
On Saturday, 2 June 2018 12:26:03 CEST, Greg V 
 wrote:


...
cyapa is indeed not the right driver either. The "cy" is for Cypress. 
That's the touchpad found in e.g. the Acer C720.


...


Side note:

I own three C720, they all came with Cypress TP. One was for repair at 
Acer.com and returned with an Elantech TP. As well, there are no spare 
parts of Cypress any more for replacement, even if the dealer claimes so, 
they came all as Elan and I returned them.


Said this, we need support for Elan in our beloved FreeBSD.

Matthias.


--
Sent from my Ubuntu phone
http://www.unixarea.de/
___
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: panic: invalid bcd 194

2018-01-02 Thread Matthias Apitz

On Tuesday, 2 January 2018 16:26:31 CET, Kurt Jaeger  wrote:

Hi!

I've added one more printf to see what is coming as year from 
BCD. The code
is attached below and bcd.year comes out as 24 (decimal) which 
is 0x18. I.e. it

seems that the year from 2018 is stored in hex as 0x18, or?


It's actually BCD code:

https://en.wikipedia.org/wiki/Binary-coded_decimal



So something must be wrong in the conversion into binary because the date 
ends up as in year 1970.






--
Sent from my Ubuntu phone
http://www.unixarea.de/
___
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: panic: invalid bcd 194

2018-01-02 Thread Matthias Apitz
El día martes, enero 02, 2018 a las 02:00:20p. m. +0100, Matthias Apitz 
escribió:

> # cp /usr/obj/usr/src/sys/GENERIC/kernel /boot/kernel/kernel
> 
> The kernel boots fine as:
> 
> FreeBSD c720-r314251 12.0-CURRENT FreeBSD 12.0-CURRENT #2 r314251M: Tue Jan  
> 2 12:53:31 CET 2018 guru@c720-r314251:/usr/obj/usr/src/sys/GENERIC  amd64
> 
> but: while the current date is read with the correct time, the year is 1970:
> 
> # date
> Tue Jan  2 1970, 13:45:24 CET
> 
> One can set the date/time with the date(1) command or ntpdate.
> 
> The debug messages are (the first line is from boot, the others from the
> date or ntpdate):
> 
> # grep DEBUG /var/log/messages
> Jan  2 13:43:02 c720-r314251 kernel: BCD DEBUG: atrtc_gettime() entry
> Jan  2 13:43:02 c720-r314251 kernel: BCD DEBUG: atrtc_gettime() entry
> Jan  2 13:44:00 c720-r314251 kernel: BCD DEBUG: atrtc_set() entry


I've added one more printf to see what is coming as year from BCD. The code
is attached below and bcd.year comes out as 24 (decimal) which is 0x18. I.e. it
seems that the year from 2018 is stored in hex as 0x18, or?


Jan  2 15:08:02 c720-r314251 kernel: BCD DEBUG: atrtc_gettime() entry without 
USE_RTC_CENTURY
Jan  2 15:08:02 c720-r314251 kernel: BCD DEBUG: atrtc_gettime() bct.year=24
Jan  2 15:13:00 c720-r314251 kernel: BCD DEBUG: atrtc_set() entry without 
USE_RTC_CENTURY
Jan  2 15:14:34 c720-r314251 kernel: BCD DEBUG: atrtc_set() entry without 
USE_RTC_CENTURY

static int
atrtc_gettime(device_t dev, struct timespec *ts)
{
struct bcd_clocktime bct;
#ifdef USE_RTC_CENTURY
printf("BCD DEBUG: atrtc_gettime() entry with USE_RTC_CENTURY\n");
#else
printf("BCD DEBUG: atrtc_gettime() entry without USE_RTC_CENTURY\n");
#endif

/* Look if we have a RTC present and the time is valid */
if (!(rtcin(RTC_STATUSD) & RTCSD_PWR)) {
device_printf(dev, "WARNING: Battery failure indication\n");
return (EINVAL);
}

/*
 * wait for time update to complete
 * If RTCSA_TUP is zero, we have at least 244us before next update.
 * This is fast enough on most hardware, but a refinement would be
 * to make sure that no more than 240us pass after we start reading,
 * and try again if so.
 */
while (rtcin(RTC_STATUSA) & RTCSA_TUP)
continue;
critical_enter();
bct.sec  = rtcin(RTC_SEC);
bct.min  = rtcin(RTC_MIN);
bct.hour = rtcin(RTC_HRS);
bct.day  = rtcin(RTC_DAY);
bct.mon  = rtcin(RTC_MONTH);
bct.year = rtcin(RTC_YEAR);
#ifdef USE_RTC_CENTURY
bct.year |= rtcin(RTC_CENTURY) << 8;
#endif
critical_exit();
/* dow is unused in timespec conversion and we have no nsec info. */
bct.dow  = 0;
bct.nsec = 0;
printf("BCD DEBUG: atrtc_gettime() bct.year=%d\n", bct.year);
return (clock_bcd_to_ts(, ts));
}

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/   
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


signature.asc
Description: PGP signature


Re: panic: invalid bcd 194

2018-01-02 Thread Matthias Apitz
El día lunes, enero 01, 2018 a las 05:02:42p. m. -0700, Ian Lepore escribió:

> Okay, I've created a pair of patches for this.  The first adds some
> common support routines usable by all RTC drivers with BCD hardware.
>  The second one converts the atrtc driver to use those routines.  The
> common code was tested using an i2c RTC chip, but I don't have an x86
> testbed, so the atrtc patch is currently untested (it compiles).
> 
> The patches are available in a pair of phabricator reviews, plus I'll
> attach them to this mail.  If the list scrubs the attachements, you can
> download the patches from the phab urls below, just hit the Actions
> button and look for Download Raw Diff.
> 
> https://reviews.freebsd.org/D13730
> https://reviews.freebsd.org/D13731

Ian, I've applied your patches by hand to the kernel source r314251 and
added in addition two printf's to atrtc.c to see the entry in
atrtc_gettime() and atrtc_set(). I've compiled the kernel with

# make buildworld -DNO_CLEAN

and copied over the new kernel with 

# cp /usr/obj/usr/src/sys/GENERIC/kernel /boot/kernel/kernel

The kernel boots fine as:

FreeBSD c720-r314251 12.0-CURRENT FreeBSD 12.0-CURRENT #2 r314251M: Tue Jan  2 
12:53:31 CET 2018 guru@c720-r314251:/usr/obj/usr/src/sys/GENERIC  amd64

but: while the current date is read with the correct time, the year is 1970:

# date
Tue Jan  2 1970, 13:45:24 CET

One can set the date/time with the date(1) command or ntpdate.

The debug messages are (the first line is from boot, the others from the
date or ntpdate):

# grep DEBUG /var/log/messages
Jan  2 13:43:02 c720-r314251 kernel: BCD DEBUG: atrtc_gettime() entry
Jan  2 13:43:02 c720-r314251 kernel: BCD DEBUG: atrtc_gettime() entry
Jan  2 13:44:00 c720-r314251 kernel: BCD DEBUG: atrtc_set() entry

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/   
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


signature.asc
Description: PGP signature


Re: panic: invalid bcd 194

2018-01-01 Thread Matthias Apitz
El día lunes, enero 01, 2018 a las 09:57:23a. m. +0100, Kurt Jaeger escribió:

> Hi!
> 
> > For the moment we solved the issue by booting some older r28
> > memstick, writing a correct date with ntpdate into the RTC and rebooted
> > without poweroff. It seems that the RTC survives even some short
> > powercyle.
> > 
> > The CMOS battery is soldered on the motherboard of the Acer C720, i.e.
> > no chance to be replaced.
> > 
> > The issue must be fixed in FreeBSD, i.e. it should boot even with a
> > broken RTC. Should I file a PR for this?
> 
> Yes, please file a PR.

done.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224813

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/   
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


signature.asc
Description: PGP signature


Re: panic: invalid bcd 194

2018-01-01 Thread Matthias Apitz
El día domingo, diciembre 31, 2017 a las 10:19:50a. m. -0700, Ian Lepore 
escribió:

> > I will let the C720 over night under power while sitting in the boot menu,
> > maybe this will fix the RTC battery issue.
> > 
> 
> Last time I worked on RTC stuff, cleaning this up got put on my "to-do
> some day" list.  I think maybe that day has arrived.
> 
> -- Ian

For the moment we solved the issue by booting some older r28
memstick, writing a correct date with ntpdate into the RTC and rebooted
without poweroff. It seems that the RTC survives even some short
powercyle.

The CMOS battery is soldered on the motherboard of the Acer C720, i.e.
no chance to be replaced.

The issue must be fixed in FreeBSD, i.e. it should boot even with a
broken RTC. Should I file a PR for this?

I'm happy to test any patch for this.

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/   
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


signature.asc
Description: PGP signature


Re: panic: invalid bcd 194

2017-12-31 Thread Matthias Apitz
El día sábado, diciembre 30, 2017 a las 10:48:19p. m. +0100, Matthias Apitz 
escribió:

> El día sábado, diciembre 30, 2017 a las 11:11:54p. m. +0200, Konstantin 
> Belousov escribió:
> 
> > > > > static inline u_char
> > > > > bcd2bin(int bcd)
> > > > > {
> > > > > 
> > > > > KASSERT(bcd >= 0 && bcd < LIBKERN_LEN_BCD2BIN,
> > > > > ("invalid bcd %d", bcd));
> > > > > return (bcd2bin_data[bcd]);
> > > > > }
> > > > > 

> > For an immediate relief, enter the BIOS setup and set up the date.  Try to
> > change it even if the BIOS date looks fine.
> > 
> > artc(4) should do more validation of the date read from CMOS, but this is
> > a known issue.
> 
> The problem with this hardware (Acer C720 Chromebook) is, there is no
> BIOS setup, only somekind of SeaBIOS w/o any setup. Btw: An older
> CURRENT from an USB key r285885 boots fine.


I have got a hint about that the problem showed up already in March this
year, even with some comment of mine in this thread:

http://freebsd.1045724.x6.nabble.com/panic-invalid-bcd-xxx-td6170480.html

In this tread is mentioned a patch as:

> cem@ posted this patch:
>
> http://dpaste.com/1K2W05E
>
> If someone can test it, I'll gladly commit it.  The real-time clock will
> likely be wrong, but it won't panic with INVARIANTS.

but the link is expired. Has got someone this patch? I checked the SVN
for the file sys/sys/libkern.h there is no relevant change since March
2017. (cc'ed cem@)

I will let the C720 over night under power while sitting in the boot menu,
maybe this will fix the RTC battery issue.

Thanks

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/   
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


signature.asc
Description: PGP signature


Re: panic: invalid bcd 194

2017-12-30 Thread Matthias Apitz
> > 
> > $ vim sys/sys/libkern.h
> > ...
> > #define LIBKERN_LEN_BCD2BIN 154
> > #define LIBKERN_LEN_BIN2BCD 100
> > #define LIBKERN_LEN_HEX2ASCII   36
> > 
> > static inline u_char
> > bcd2bin(int bcd)
> > {
> > 
> > KASSERT(bcd >= 0 && bcd < LIBKERN_LEN_BCD2BIN,
> > ("invalid bcd %d", bcd));
> > return (bcd2bin_data[bcd]);
> > }
> > 
> > Any idea what could be damaged the system and what to do or check before
> > re-setup?
> 
> Show the backtrace.

attached as JPG (sorry);

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/   
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


signature.asc
Description: PGP signature


Re: panic: invalid bcd 194

2017-12-30 Thread Matthias Apitz
El día sábado, diciembre 30, 2017 a las 11:11:54p. m. +0200, Konstantin 
Belousov escribió:

> > > > static inline u_char
> > > > bcd2bin(int bcd)
> > > > {
> > > > 
> > > > KASSERT(bcd >= 0 && bcd < LIBKERN_LEN_BCD2BIN,
> > > > ("invalid bcd %d", bcd));
> > > > return (bcd2bin_data[bcd]);
> > > > }
> > > > 
> > > > Any idea what could be damaged the system and what to do or check before
> > > > re-setup?
> > > 
> > > Show the backtrace.
> > 
> > Thanks, here we have it as photo: 
> > http://www.unixarea.de/download_238222137_147226.jpg
> 
> For an immediate relief, enter the BIOS setup and set up the date.  Try to
> change it even if the BIOS date looks fine.
> 
> artc(4) should do more validation of the date read from CMOS, but this is
> a known issue.

The problem with this hardware (Acer C720 Chromebook) is, there is no
BIOS setup, only somekind of SeaBIOS w/o any setup. Btw: An older
CURRENT from an USB key r285885 boots fine.

Any hints?

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/   
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


signature.asc
Description: PGP signature


Re: panic: invalid bcd 194

2017-12-30 Thread Matthias Apitz
El día sábado, diciembre 30, 2017 a las 10:44:57p. m. +0200, Konstantin 
Belousov escribió:

> On Sat, Dec 30, 2017 at 09:03:17PM +0100, Matthias Apitz wrote:
> > 
> > Hello,
> > 
> > I've got an older Acer C720 with r314251, which was not booted for some 
> > time,
> > and now panics on boot, also in single user mode, saying:
> > 
> > ...
> > Dec 30 19:54:26 c720-r314251 kernel: ada0: Command Queueing enabled
> > Dec 30 19:54:26 c720-r314251 kernel: ada0: 244198MB (500118192 512 byte 
> > sectors)
> > Dec 30 19:54:26 c720-r314251 kernel: WARNING: WITNESS option enabled, 
> > expect reduced performance.
> > Dec 30 19:54:26 c720-r314251 kernel: Trying to mount root from 
> > ufs:/dev/ada0p2 [rw,noatime]...
> > panic: invalid bcd 194
> > ...
> > 
> > The message comes from 
> > 
> > $ find * -type f -exec fgrep "invalid bcd" {} /dev/null \;
> > sys/sys/libkern.h:  ("invalid bcd %d", bcd));
> > 
> > $ vim sys/sys/libkern.h
> > ...
> > #define LIBKERN_LEN_BCD2BIN 154
> > #define LIBKERN_LEN_BIN2BCD 100
> > #define LIBKERN_LEN_HEX2ASCII   36
> > 
> > static inline u_char
> > bcd2bin(int bcd)
> > {
> > 
> > KASSERT(bcd >= 0 && bcd < LIBKERN_LEN_BCD2BIN,
> > ("invalid bcd %d", bcd));
> > return (bcd2bin_data[bcd]);
> > }
> > 
> > Any idea what could be damaged the system and what to do or check before
> > re-setup?
> 
> Show the backtrace.

Thanks, here we have it as photo: 
http://www.unixarea.de/download_238222137_147226.jpg

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/   
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


signature.asc
Description: PGP signature


panic: invalid bcd 194

2017-12-30 Thread Matthias Apitz

Hello,

I've got an older Acer C720 with r314251, which was not booted for some time,
and now panics on boot, also in single user mode, saying:

...
Dec 30 19:54:26 c720-r314251 kernel: ada0: Command Queueing enabled
Dec 30 19:54:26 c720-r314251 kernel: ada0: 244198MB (500118192 512 byte sectors)
Dec 30 19:54:26 c720-r314251 kernel: WARNING: WITNESS option enabled, expect 
reduced performance.
Dec 30 19:54:26 c720-r314251 kernel: Trying to mount root from ufs:/dev/ada0p2 
[rw,noatime]...
panic: invalid bcd 194
...

The message comes from 

$ find * -type f -exec fgrep "invalid bcd" {} /dev/null \;
sys/sys/libkern.h:  ("invalid bcd %d", bcd));

$ vim sys/sys/libkern.h
...
#define LIBKERN_LEN_BCD2BIN 154
#define LIBKERN_LEN_BIN2BCD 100
#define LIBKERN_LEN_HEX2ASCII   36

static inline u_char
bcd2bin(int bcd)
{

KASSERT(bcd >= 0 && bcd < LIBKERN_LEN_BCD2BIN,
("invalid bcd %d", bcd));
return (bcd2bin_data[bcd]);
}

Any idea what could be damaged the system and what to do or check before
re-setup?

Thanks

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/   
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


signature.asc
Description: PGP signature


updating /usr/ports to HEAD in a jail r318593 (May 2017)

2017-11-11 Thread Matthias Apitz

Hello,

My poudriere oven runs as kernel:
$ uname -a
FreeBSD jet 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r318593: Sun May 21 22:05:29 
...

and I have a jail on it with exact this kernel r318593. Is it save to
update ports in this jail to HEAD (as of today) or are there some
incompatible changes in the ports tree which need a newer kernel? I
glanced through /usr/ports/UPDATING but could no see anything. Any
pointers? 

Thanks

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


signature.asc
Description: PGP signature


Re: mount_smbfs gives error when stored crypted pw is used

2017-06-07 Thread Matthias Apitz
El día miércoles, junio 07, 2017 a las 02:35:31p. m. +0200, Matthias Apitz 
escribió:

> I have located the bug in /usr/src/contrib/smbfs/lib/smb/subr.c 
> 
> The printf(3C) calls have been added for debugging; the bug is the
> addition of 13 after crypting every char which let the mask used in ^ 
> operation
> exceeding 256, i.e. more than one byte, if the string to be crypted is long
> enough. The two lines added:
> 
> if (pos > 256)
> pos = pos-256;
> 
> fixes this issue and the crypting/decypting works fine; see below;
> 
> I'll later file a PR and propose the patch;

The PR was already made in 2009: 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=132302
has a patch attached (nearly the same solution as I have found), but was
never ci'ed :-(

matthias


-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
8. Mai 1945: Wer nicht feiert hat den Krieg verloren.
8 de mayo de 1945: Quien no festeja perdió la Guerra.
May 8, 1945: Who does not celebrate lost the War.


signature.asc
Description: PGP signature


Re: mount_smbfs gives error when stored crypted pw is used

2017-06-07 Thread Matthias Apitz
I have located the bug in /usr/src/contrib/smbfs/lib/smb/subr.c 

The printf(3C) calls have been added for debugging; the bug is the
addition of 13 after crypting every char which let the mask used in ^ operation
exceeding 256, i.e. more than one byte, if the string to be crypted is long
enough. The two lines added:

if (pos > 256)
pos = pos-256;

fixes this issue and the crypting/decypting works fine; see below;

I'll later file a PR and propose the patch;

matthias

char *
smb_simplecrypt(char *dst, const char *src)
{
int ch, pos;
char *dp;

printf("smb_simplecrypt(): pw: [%s]\n", src);

if (dst == NULL) {
dst = malloc(4 + 2 * strlen(src));
if (dst == NULL)
return NULL;
}
dp = dst;
*dst++ = '$';
*dst++ = '$';
*dst++ = '1';
pos = 27;
while (*src) {
ch = *src++;
printf("ch [%c] --> ", ch);
if (isascii(ch))
ch = (isupper(ch) ? ('A' + (ch - 'A' + 13) % 26) :
  islower(ch) ? ('a' + (ch - 'a' + 13) % 26) : ch);
ch ^= pos;
pos += 13;
if (pos > 256)
pos = pos-256;
sprintf(dst, "%02x", ch);
printf("0x%02x next ^mask (pos): 0x%02x\n", ch, pos);
dst += 2;
}
*dst = 0;
return dp;
}

$ ./smbpw
smb_simplecrypt(): pw: [1234567890-1-1234567]
ch [1] --> 0x2a next ^mask (pos): 0x28
ch [2] --> 0x1a next ^mask (pos): 0x35
ch [3] --> 0x06 next ^mask (pos): 0x42
ch [4] --> 0x76 next ^mask (pos): 0x4f
ch [5] --> 0x7a next ^mask (pos): 0x5c
ch [6] --> 0x6a next ^mask (pos): 0x69
ch [7] --> 0x5e next ^mask (pos): 0x76
ch [8] --> 0x4e next ^mask (pos): 0x83
ch [9] --> 0xba next ^mask (pos): 0x90
ch [0] --> 0xa0 next ^mask (pos): 0x9d
ch [-] --> 0xb0 next ^mask (pos): 0xaa
ch [1] --> 0x9b next ^mask (pos): 0xb7
ch [-] --> 0x9a next ^mask (pos): 0xc4
ch [1] --> 0xf5 next ^mask (pos): 0xd1
ch [2] --> 0xe3 next ^mask (pos): 0xde
ch [3] --> 0xed next ^mask (pos): 0xeb
ch [4] --> 0xdf next ^mask (pos): 0xf8
ch [5] --> 0xcd next ^mask (pos): 0x05
ch [6] --> 0x33 next ^mask (pos): 0x12
ch [7] --> 0x25 next ^mask (pos): 0x1f
cp: [$$12a1a06767a6a5e4ebaa0b09b9af5e3eddfcd3325]
smb_simpledecrypt(): hash: [$$12a1a06767a6a5e4ebaa0b09b9af5e3eddfcd3325] gives 
clear [1234567890-1-1234567]


-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
8. Mai 1945: Wer nicht feiert hat den Krieg verloren.
8 de mayo de 1945: Quien no festeja perdió la Guerra.
May 8, 1945: Who does not celebrate lost the War.


signature.asc
Description: PGP signature


Re: mount_smbfs gives error when stored crypted pw is used

2017-06-06 Thread Matthias Apitz
El día martes, junio 06, 2017 a las 12:00:34p. m. +0200, Matthias Apitz 
escribió:

> 
> Hello,
> 
> At work I have to run FreeBSD (12-CURRENT, amd64) in vbox on Win7 host
> and used successful mount_smbfs to mount the hosts disk to FreeBSD. This
> worked fine until the last password change of the domain pw we have todo
> every 12 weeks or so.
> 
> Now the new crypted and stored pw from /etc/nsmb.conf is not accepted
> anymore. In detail, when I do:
> 
> ...

I looked into the sources in src/contrib/smbfs/lib/smb to understand how
the hashed pw is translated to clear text and wrote a small test pgm
which uses the same function of the /usr/lib/libsmb.so


$ cc -o smbpw smbpw.c -l smb

I now crypt a dummy pw with the following chars '1234567890-1-1234567':

$ smbutil crypt 1234567890-1-1234567
$$12a1a06767a6a5e4ebaa0b09b9af5e3eddfcd1312

the resulting hash gives retranslated by smb_simpledecrypt():

$ ./smbpw 
smb_simpledecrypt(): hash: [$$12a1a06767a6a5e4ebaa0b09b9af5e3eddfcd1312] gives 
clear [1234567890-1-12345]

i.e. the last two chars are missing.

$ cat smbpw.c

#include 

int
smb_simpledecrypt(char *dst, const char *src);

int main()
{

char *hash = "$$12a1a06767a6a5e4ebaa0b09b9af5e3eddfcd1312";
char clear[256];

clear[0] = '\0';

smb_simpledecrypt(clear, hash);

printf("smb_simpledecrypt(): hash: [%s] gives clear [%s]\n", hash, clear);

}

This seems to be an issue in the libsmb...

matthias



-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
8. Mai 1945: Wer nicht feiert hat den Krieg verloren.
8 de mayo de 1945: Quien no festeja perdió la Guerra.
May 8, 1945: Who does not celebrate lost the War.


signature.asc
Description: PGP signature


Re: buildworld not working with MAKEOBJDIRPREFIX

2017-05-16 Thread Matthias Apitz
El día Tuesday, May 16, 2017 a las 02:18:36PM +0200, O. Hartmann escribió:

> On Tue, 16 May 2017 09:39:11 +0100
> Roger Pau Monné <roger@citrix.com> wrote:
> 
> > Hello,
> > 
> > I'm trying to build world as a regular user, using sources fetched into my
> > home directory and a different object directory. The rune I'm using to build
> > is:
> > 
> > $ cd /home/royger/buildjob/freebsd
> > $ make -j30 buildworld MAKEOBJDIRPREFIX=/home/royger/buildjob/obj/
> 
> As far as I know, in this construct, MAKEOBJDIRPREFIX is an argument to make,
> but MAKEOBJDIRPREFIX is strictly required to be set in the environment!

I used it many times that way, as well

# make installworld DESTDIR=/mnt

This should work. Can you try with a smaller -j value?

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/ccid--export-key-guru.pub
8. Mai 1945: Wer nicht feiert hat den Krieg verloren.
8 de mayo de 1945: Quien no festeja perdió la Guerra.
May 8, 1945: Who does not celebrate lost the War.
___
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"

debugging webcamd in CURRENT

2017-03-20 Thread Matthias Apitz

Hello,

I have a very recent 12-CURRENT on amd64 (r314251) with all ports from beginning
of March.

While testing multimedia/webcamd in debug mode it says:

# /usr/local/sbin/webcamd -i 0 -d ugen0.2 -U webcamd -G webcamd -H
: USB HID core driver
Linux video capture interface: v2.00
IR NEC protocol handler initialized
IR RC5(x/sz) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR SANYO protocol handler initialized
IR LIRC bridge handler initialized
IR XMP protocol handler initialized
b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded 
successfully
uvcvideo: Unable to create debugfs directory

USB Video Class driver (1.1.1)
cpia2: V4L-Driver for Vision CPiA2 based cameras v3.0.1
pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner
pvrusb2: Debug mask is 31 (0x1f)
USBVision USB Video Device Driver for Linux : 0.9.11
em28xx: Registered (Em28xx v4l2 Extension) extension
em28xx: Registered (Em28xx dvb Extension) extension
Attached to ugen0.2[0]
uvcvideo: Found UVC 1.00 device HD WebCam (1bcf:2c67)
Waiting for HAL USB device.
Creating /dev/video0
uvcvideo: Failed to submit URB 0 (-32).


Questions about this:

1. Why it is unable to create the debugfs directory?
2. The UVC driver in
multimedia/webcamd/work/webcamd-4.8.0.4/media_tree/drivers/media/usb/uvc
is from between 2013-2016, is there any more recent version?
3. Why is it sometimes failing with 'Failed to submit URB 0 (-32)'?

Thanks

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
___
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: update an older i386 CURRENT system to amd64 CURRENT

2017-03-16 Thread Matthias Apitz
On Thursday, 16 March 2017 15:25:10 CET, Allan Jude  
wrote:




The problem is that the build system has built a cross compiler in
/usr/obj that it uses to do the building etc, and it is 64bit. Your
32bit OS cannot run it (gives Exec format error).



Thanks for all the replies I got.

Meanwhile I booted from a r314251 memstick, and all is installed fine.

matthias





--
Sent from my Ubuntu phone
http://www.unixarea.de/
___
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"


update an older i386 CURRENT system to amd64 CURRENT

2017-03-16 Thread Matthias Apitz
_TYPE.
*** Error code 1


Is there a way to use this /usr/src and pre-compiled /usr/obj on an i386
host for update? Or do I have to use a complete recompile or even
reinstall, based on a 64-bit memstick system?

Thanks

matthias


-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
___
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: AMD CPU/APU temperature driver

2017-03-06 Thread Matthias Apitz
El día Monday, March 06, 2017 a las 05:04:31AM +0300, Rozhuk Ivan escribió:

> Hi!
> 
> 
> New amdtemp driver needs more testers!
> 
> 
> https://reviews.freebsd.org/D9759
> 
> Fast buld/install:
> ...download and apply patch...
> kldunload amdtemp
> cd /usr/src/sys/modules/amdtemp/
> make
> make install
> make cleandir
> kldload amdtemp
> 
> 
> rus/eng: http://netlab.dhis.org/wiki/ru:software:freebsd:amdtemp

Hi,

The English version of the Wiki gives only: This topic does not exist
yet. Is there an English version?

Thanks

matthias


-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Aus "Nie wieder Krieg!" wurde "Nie wieder Krieg ohne Deutschlands Truppen"
The "No wars anymore!" changed now to "No wars anymore without German battle 
groups!"
El "¡Nunca jamás guerra!" ha cambiado a "¡Nunca jamás guerra sin tropas 
alemanas!" 
___
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: panic: invalid bcd xxx

2017-03-02 Thread Matthias Apitz
On Thursday, 2 March 2017 00:37:35 CET, Michael Gmelin  
wrote:




On 2 Mar 2017, at 00:35, Adrian Chadd  wrote:

This is an emulated BIOS though, right?

I don't know if we're going to get the RTC 'bugfixed'...




It's SeaBIOS, yes. I feel like this might end up in another 
quirk/workaround solution.




I'm one of the C720 owners and  apart of Michael, I only know two users 
more running FreeBSD. The SeaBIOS in our devices. is outdated, mine from 
2013 IIRC. I dont know if there is an easy way to update this.


matthias



--
Sent from my Ubuntu phone
http://www.unixarea.de/
___
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: ISO image: where is the CLANG compiler?

2017-01-20 Thread Matthias Apitz
El d�a Friday, January 20, 2017 a las 09:39:06AM +0100, Andreas Nilsson 
escribi�:

> Good good. I am in no way opposed to the "infrastructure" change of
> separating the targets, sounds like a bit of makefile-fun actually. And
> having tools to create memsticks from ones preferred environment would be
> sweet.
> 
> Maybe someone could add a target in the makefiles for a rescue image, which
> basically would be the complete FreeBSD system one would get after untaring
> base, kernel and src?

One can install a complete system into a target directory:

# mkdir /foo
# make install DESTDIR=/foo

and use the scripts in src/release/*/make-memstick.sh
to create an image of the system below /foo

What else do you need?

    matthias

-- 
Matthias Apitz   |  /"\   ASCII Ribbon Campaign:
E-mail: g...@unixarea.de |  \ /   - No HTML/RTF in E-mail
WWW: http://www.unixarea.de/ |   X- No proprietary attachments
phone: +49-176-38902045  |  / \   - Respect for open standards
 | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign
___
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: ISO image: where is the CLANG compiler?

2017-01-19 Thread Matthias Apitz
El día Thursday, January 19, 2017 a las 10:16:46AM +0100, O. Hartmann escribió:

> I created images on CURRENT of my own - they all lack in the ability of having
> the necessary tools aboard. So I consider every image useless for rescue
> operations except, maybe, the DVD image - but this one is not provided 
> anymore.
> For what reason? Time? Accepted. Space/disk usage? Well, welcome back in the
> stoneage of computer technology ... 

No. The process I'm using to create an image for an USB stick leads to a
complete system from which you can even, after booting it, 'make install...'
to another system mounted on /mnt to the booted USB stick. You can even
enrich the USB stick with 'pkg install ...' up to a complete running KDE
desktop system, all running from the USB stick, to test, for example, a
new hardware if it fits your needs. The stick must be of some 16
marketing-GB, or bigger.

This has nothing todo with stoneage, but is just a matter of preparing
something for your needs. Again, let me know if you need this guide.

    matthias



-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Wo ist der antiimperialistische Schutzwall, wenn man ihn braucht? 
US-Panzertransport durch ex-DDR"
"Where is the anti-imperialistic  wall, if it's needed? Transport of US-tanks 
through the ex-GDR"
https://deutsch.rt.com/kurzclips/45282-us-panzertransporte-durch-ex-ddr/
___
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: ISO image: where is the CLANG compiler?

2017-01-18 Thread Matthias Apitz
El día Wednesday, January 18, 2017 a las 08:00:04PM -0500, Allan Jude escribió:

> On 2017-01-18 14:37, O. Hartmann wrote:
> > Am Wed, 18 Jan 2017 16:38:32 +0100
> > Matthias Apitz <g...@unixarea.de> schrieb:
> > 
> >> Why you do not just boot from USB some mem stick image, mount some disk
> >> space to /mnt, svn checkout CURRENT to /mnt and build a booteable system
> >> (world and kernel) and install to DESTDIR=/mnt ?
> >>
> >> I do not understand all this hassle?
> >>
> >>matthias
> >>
> > 
> > Wow!
> > 
> > As I initially stated, that is EXACTLY what I was inclined to do except the 
> > fact that I
> > had already an intact /usr/obj and usr/src with a complete compiled system.
> > 
> > I booted from mem stick and I was lost due to no cc!
> > 
> > Even for "make installworld" it seems I have to rely on the compiler. And 
> > the images
> > (ISO, memstick et cetera) provided these days do not contain any clang.

Yes, you will need it and it will complain about missing it, if for
example you moved 'obj and 'src' to other dirs after 'make build...'

But, in your case the mem image really is lacking the cc/clang; I
fetched the image an did:


# mdconfig -a -t vnode -u 1 -f 
~guru/Downloads/FreeBSD-11.0-RELEASE-amd64-memstick.img
# mount -o ro /dev/md1p3 /mnt
# find /mnt -name clang
/mnt/usr/share/doc/llvm/clang
/mnt/usr/lib/clang
/mnt/usr/lib/debug/usr/lib/clang
# find /mnt -name cc
/mnt/usr/include/netinet/cc

With this img  alone, you can't compile a system :-(

Setup a system from DVD and build your own image containing a complete
system on an USB key; with this boot your damaged system, recompile and
reinstall world and kernel. If you (O. Hartmann) need a step by step
guide, I could send it to you.

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Wo ist der antiimperialistische Schutzwall, wenn man ihn braucht? 
US-Panzertransport durch ex-DDR"
"Where is the anti-imperialistic  wall, if it's needed? Transport of US-tanks 
through the ex-GDR"
https://deutsch.rt.com/kurzclips/45282-us-panzertransporte-durch-ex-ddr/
___
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: ISO image: where is the CLANG compiler?

2017-01-18 Thread Matthias Apitz

(I adjuested To/cc)

El día Wednesday, January 18, 2017 a las 08:37:26PM +0100, O. Hartmann escribió:

> Wow!
> 
> As I initially stated, that is EXACTLY what I was inclined to do except the 
> fact that I
> had already an intact /usr/obj and usr/src with a complete compiled system.
> 
> I booted from mem stick and I was lost due to no cc!
> 
> Even for "make installworld" it seems I have to rely on the compiler. And the 
> images
> (ISO, memstick et cetera) provided these days do not contain any clang.
> 
> So, I tried /usr/src/release ... for the first time. The image does also not 
> contain the
> necessary tools for a full "make installworld installkernel" - not to speak of
> "compiling" world. I dodn't work (at least for me). 

What gives:

# rm -r /usr/obj
# cd /usr/src
# make buildworld
# make buildkernel

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Wo ist der antiimperialistische Schutzwall, wenn man ihn braucht? 
US-Panzertransport durch ex-DDR"
"Where is the anti-imperialistic  wall, if it's needed? Transport of US-tanks 
through the ex-GDR"
https://deutsch.rt.com/kurzclips/45282-us-panzertransporte-durch-ex-ddr/
___
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: ISO image: where is the CLANG compiler?

2017-01-18 Thread Matthias Apitz
Why you do not just boot from USB some mem stick image, mount some disk
space to /mnt, svn checkout CURRENT to /mnt and build a booteable system
(world and kernel) and install to DESTDIR=/mnt ?

I do not understand all this hassle?

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Wo ist der antiimperialistische Schutzwall, wenn man ihn braucht? 
US-Panzertransport durch ex-DDR"
"Where is the anti-imperialistic  wall, if it's needed? Transport of US-tanks 
through the ex-GDR"
https://deutsch.rt.com/kurzclips/45282-us-panzertransporte-durch-ex-ddr/
___
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: [request for testing] isl, cyapa on chromebooks

2016-10-10 Thread Matthias Apitz
El día Monday, October 10, 2016 a las 09:26:26AM -0600, Warner Losh escribió:

> I see no reason not to start the table right away based on
> smbios.sys.product and other criteria. I don't think we need all the
> matches that Linux uses, but we can expand the table if we find it so.
> Why have a stop gap that's a table that we kludge together when the
> real table is of comparable difficulty and wouldn't need to be
> reworked.

Please let us together concentrate on getting other i2c devices working,
like the Elan TouchPad, because I fear that newer Chromebooks are all
equipped with this and not with the Cyapa anymore.

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Einheitsfeier? Nein, danke! Kann ich bitte mein Land wiederhaben und am 7. 
Oktober feiern.
___
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: [request for testing] isl, cyapa on chromebooks

2016-10-09 Thread Matthias Apitz


Thanks. Changing device.hints to

iicbus14
iicbus15

makes cyapa(4) attaching and moused working fine. I will later install xorg 
into this memstick.


matthias




--
Sent from my Ubuntu phone
http://www.unixarea.de/
___
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: [request for testing] isl, cyapa on chromebooks

2016-10-09 Thread Matthias Apitz
El día Sunday, October 09, 2016 a las 01:53:24AM +0200, Michael Gmelin escribió:

> Would I maybe make sense to have man pages for specific laptops (instead
> of the "FreeBSD Laptop" page, blogs on the internet and Wiki pages).
> 
> Just thinking that after this change, people will need to know the
> correct addresses for device.hints to make isl and cyapa work, and
> putting things like that (and other hints, e.g. to route the Intel HDA
> correctly) into a man page ("apropos c720") would be the next best
> thing to having it work out of the box.

Good idea. The problem with such an approach is, that new laptops get
only inserted into man pages when some maintainer/approver does so and
seldom if someone brings a new device to working (more or less) with
FreeBSD.

In the past (some 15 years ago) there was a database and a web frotnend
where people (everyone) could insert/update a new working device. It was
here: http://laptop.bsdgroup.de/freebsd/ but the site is offline for
many year. I even tried and contacted the provide of 'bsdgroup.de' to
get a copy of the database, w/o any luck.

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Einheitsfeier? Nein, danke! Kann ich bitte mein Land wiederhaben und am 7. 
Oktober feiern.
___
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: [request for testing] isl, cyapa on chromebooks

2016-10-09 Thread Matthias Apitz
El día Saturday, October 08, 2016 a las 10:17:07PM +0300, Andriy Gapon escribió:

> On 08/10/2016 21:07, Matthias Apitz wrote:
> > I have now produced a memstick with (unpatched) r306769 of October 6. It 
> > boots
> > fine in my Acer C720 Chromebook and the moused is working fine with the
> > cyapa(4) driver. I will apply tomorrow the above v4 patch or is there
> > anything newer? And will test/report.
> 
> v4 is the latest.  Thanks!

The patch applies cleanly, the 'make buildkernel' does fine and system
boots, but cyapa(4) can not bring the device out of bootstrap. The verbose dmesg
is here http://www.unixarea.de/dmesg-00.txt 

And yes, I have in /boot/device.hints:

...
# The change moves the drivers from the SMBus to the I2C bus and as such some
# configuration changes are required.
# Namely, you will now need iicbus driver either in the kernel configuration or 
as
# a module.  For now the smbus driver is also required.
# You also need to add some entries to /boot/device.hints:
# 
hint.isl.0.at="iicbus0"
hint.isl.0.addr=0x88
hint.isl.1.at="iicbus1"
hint.isl.1.addr=0x88
hint.cyapa.0.at="iicbus0"
hint.cyapa.0.addr=0xce
hint.cyapa.1.at="iicbus1"
hint.cyapa.1.addr=0xce
# 
# The hints are required because auto-probing (either via the bus enumeration or
# self-identification) is disabled for now for safety reason.
# Also, as I understand, the Intel chipset used in the supported Chromebooks
# provides to i2c buses (possibly in addition in an smbus) and I am not sure on
# which of the i2c buses the devices reside.

Please let me know what to check/debug.

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Einheitsfeier? Nein, danke! Kann ich bitte mein Land wiederhaben und am 7. 
Oktober feiern.
___
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: [request for testing] isl, cyapa on chromebooks

2016-10-08 Thread Matthias Apitz
On Saturday, 8 October 2016 23:54:27 CEST, Warner Losh  
wrote:

Speaking of Chromebooks, what's the best way to put FreeBSD onto one?



Set it to developer mode or Legacy boot, boot and install 11-C or 12-C from 
USB.


matthias



--
Sent from my Ubuntu phone
http://www.unixarea.de/
___
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: [request for testing] isl, cyapa on chromebooks

2016-10-08 Thread Matthias Apitz
El día Thursday, October 06, 2016 a las 11:12:27AM +0300, Andriy Gapon escribió:

> On 06/10/2016 11:10, Michael Gmelin wrote:
> > 
> > 
> >> On 06 Oct 2016, at 09:48, Andriy Gapon <a...@freebsd.org> wrote:
> >>
> >>> On 06/10/2016 08:37, Andriy Gapon wrote:
> >>> The more testing the better!
> >>
> >> Based on Michael's results I've uploaded a new version:
> >> https://people.freebsd.org/~avg/ig4-i2c.v4.diff
> >>
> >>
> > 
> > Good news. Applying the last two fixes manually, isl is working now.
> 
> Great!
> 
> > I'll rebuild a kernel using the complete v4 patch on my second machine 
> > later today to test the modified cyapa driver.

I have now produced a memstick with (unpatched) r306769 of October 6. It boots
fine in my Acer C720 Chromebook and the moused is working fine with the
cyapa(4) driver. I will apply tomorrow the above v4 patch or is there
anything newer? And will test/report.

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
___
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: [request for testing] isl, cyapa on chromebooks

2016-10-05 Thread Matthias Apitz
El día Wednesday, October 05, 2016 a las 04:01:25PM +0300, Andriy Gapon 
escribió:

> On 05/10/2016 14:19, Michael Gmelin wrote:
> > 
> > ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe and
> > iicbus_attach are not.
> 
> Thank you!
> Now I think I see where I made a silly mistake.
> Please try an updated version of the patch from here
> https://people.freebsd.org/~avg/ig4-i2c.v3.diff
> It contains a fix and some cosmetic changes on top of the previous patch.

Hi Andriy,

I have an Acer C720 too, since around two years and it works fine,
thanks to Michael, with the cyapa chip. I have my C720 in daily heavy
usage, actually with r292778. Should I apply the above patch or do I
need to update before to a more recent CURRENT? I have a second C720
where I could do such test/update more easy, but this is current not in
my hands and has, after a repair at Acer, a Elan touch pad.
But I could prepare an USB key with 12-CURRENT, just for test.

Btw: What is the reason for this change of ig4/i2c/cyapa driver?

Last thing: I propose to remove freebsd-mobile@ from the thread.

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
___
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: FreeBSD 12 - subversion

2016-08-23 Thread Matthias Apitz
On Tuesday, 23 August 2016 17:24:07 CEST, Jochen Neumeister 
 wrote:

Is anyone else seeing this


uname -a
FreeBSD builder.miwibox.org 12.0-CURRENT FreeBSD 12.0-CURRENT #0
r303736: Thu Aug  4 05:34:30 UTC 2016
root@rescue:/usr/obj/usr/src/sys/MIWIBOX  amd64



/usr/ports/devel/subversion # make install clean


[schnipp]




Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1



Is the full ports tree as well on head an clean?

matthias




--
Sent from my Ubuntu phone
http://www.unixarea.de/
___
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: seldom crashes on Dell E6330 with 12-CURRENT

2016-07-26 Thread Matthias Apitz

I have moved swap to its own partition using this commands:


... it turned out, that having swap as a plane file in /usr was
not a good decission, we deleted (after making DUMPS) the 'ssdusrfs'
again, created swap and re-created 'ssdusrfs'; this must be done while
/dev/gpt/ssdusrfs is not mounted!

# gpart show -l ada0
=>   40  488397088  ada0  GPT  (233G)
 40   1024 1  ssdboot  (512K)
   1064984- free -  (492K)
   20484194304 2  ssdrootfs  (2.0G)
41963524194304 3  ssdvarfs  (2.0G)
8390656  480006144 4  ssdusrfs  (229G)
  488396800328- free -  (164K)

be carefully with the correct number of the index, in our case 4; check
the output of 'gpart show -l ada0' before doing this:

# gpart delete -i 4 ada0

create the swap partition:

# gpart add -t freebsd-swap -l ssdswap -a 1m -s 8g ada0

and the rest is our 'ssdusrfs' again:

# gpart add -t freebsd-ufs -l ssdusrfs -a 1m ada0
# newfs -U -t /dev/gpt/ssdusrfs

the new /etc/fstab should look like this:

# DeviceMountpoint  FStype  Options DumpPass#
/dev/gpt/ssdswapnoneswapsw  0   0
/dev/gpt/ssdrootfs  /   ufs rw  1   1
/dev/gpt/ssdvarfs   /varufs rw  2   2
tmpfs   /tmptmpfs   rw,mode=01777   0   0
/dev/gpt/ssdusrfs   /usrufs rw  2   2


we need gzip and some shared libs (which normaly are in /usr); I copied
them on some other system into the externals disk where the DUMP is:

# cp -p /usr/bin/gzip /usr/lib/liblzma.so.5 /usr/lib/libbz2.so.4 /mnt

now mount and restore the DUMP:

# mount tmpfs
# mount /usr
# cd /usr
# mount -o ro /dev/da0s2a /mnt

# LD_LIBRARY_PATH=/mnt export LD_LIBRARY_PATH
# gzip -dc /mnt/e6330/dumpse6330-20160726/usr.dmp.gz | restore -x -f -
# umount /mnt
# reboot



-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Wer übersieht, dass wir uns den anderen weggenommen haben und sie uns 
wiederhaben wollen,
kann von den Kämpfen der letzten Tage keinen verstehen. Und kann natürlich auch 
keinen
dieser Kämpfe bestehen." Hermann Kant in jW 1.10.1989
___
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: seldom crashes on Dell E6330 with 12-CURRENT

2016-07-26 Thread Matthias Apitz

I just got a new panic with drop to debugger after shutdown, all disks
have synced correctly, only something to page-in from swap was causing
the problem; I don't know how to get a screen-shoot from this, so I took
a picture, it's here http://www.unixarea.de/panic.jpg

Btw: how can the kernel read from a swapfile if the file system is
already unmounted?

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Wer übersieht, dass wir uns den anderen weggenommen haben und sie uns 
wiederhaben wollen,
kann von den Kämpfen der letzten Tage keinen verstehen. Und kann natürlich auch 
keinen
dieser Kämpfe bestehen." Hermann Kant in jW 1.10.1989
___
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: seldom crashes on Dell E6330 with 12-CURRENT

2016-07-25 Thread Matthias Apitz
El día Monday, July 25, 2016 a las 05:00:59PM -0700, Mark Millard escribió:

> Matthias Apitz guru at unixarea.de wrote on Mon Jul 25 16:10:52 UTC 2016 :
> 
> > On Monday, 25 July 2016 17:11:23 CEST, Eric van Gyzen  > FreeBSD.org> wrote: > 
> > > What file system are you using? 
> > UFS; I followed the good instructions about new SSD disk configuration; 
> > that's why I now have swap as plain file :-( 
> 
> Unfortunately see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206048 :
> 
> 11.0-CURRENT -r293227 (and others) arm (rpi2/BeagleBone Black) amd64 etc: 
> swapfile usage hangs; swap partition works .
> 
> As far as I know it still applies for the problems that can occur for 
> plain-file based swap files. The list of comments covers more than just armv6 
> as having example failures.
> 

Thanks for the pointer to the bug issue. I remembered, that I created
the swap file as a so called sparse file (dd ... bs=1m seek=8192 count=0) and
this is still visible with du(1):

# du -sh /usr/swap01 ; ls -lh /usr/swap01
 95M/usr/swap01
-rw---  1 root  wheel   8,0G 25 jul.  08:19 /usr/swap01

I have now unmounted the swap and re-created it with real blocks:

# swapoff -a
swapoff: removing /dev/md99 as swap device

# dd if=/dev/zero of=/usr/swap01 bs=1m count=8192
8192+0 records in
8192+0 records out
8589934592 bytes transferred in 43.594277 secs (197042712 bytes/sec)
# du -sh /usr/swap01 ; ls -lh /usr/swap01
8,0G/usr/swap01
-rw---  1 root  wheel   8,0G 26 jul.  07:24 /usr/swap01

I will first give this a try. If the crash rehappens, I will move it to
a real freebsd-swap partition.

While saying 'crash', I now remember that in the two cases which I named
'hard locked', the system was still alive in the sense of echoing typed
chars, it was only impossible to start new commands or login on another
console. This points too in the direction of a disk access or swap problem.

Thanks

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Wer übersieht, dass wir uns den anderen weggenommen haben und sie uns 
wiederhaben wollen,
kann von den Kämpfen der letzten Tage keinen verstehen. Und kann natürlich auch 
keinen
dieser Kämpfe bestehen." Hermann Kant in jW 1.10.1989
___
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: seldom crashes on Dell E6330 with 12-CURRENT

2016-07-25 Thread Matthias Apitz
On Monday, 25 July 2016 17:11:23 CEST, Eric van Gyzen 
 wrote:




What file system are you using?


UFS; I followed the good instructions about new SSD disk configuration; 
that's why I now have swap as plain file :-(



Do a full fsck (or zfs scrub).


will do a full fsck;


Try moving swap to a raw (freebsd-swap) partition so that you might get
a kernel core dump.  That will be the essential next step.


ok, I will dump /usr to some external disk, shrink
the partition, creat swap and re-create /usr



Without more details from a core dump or debugger, your best option is
to try a release or an older build.  If that works, try to find the
commit that introduced the behavior.  This will be very tedious and
time-consuming for your scenario, so definitely try getting a core dump
first.


the problem is as well: until now no further crashes had occured, i.e. it' 
difficult to see if it works or not;


matthias





--
Sent from my Ubuntu phone
http://www.unixarea.de/
___
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"


seldom crashes on Dell E6330 with 12-CURRENT

2016-07-23 Thread Matthias Apitz

Hello,

I own since July 15 a new laptop and faced 3 crashes, details see below.
What can I do to gather more information? Thanks


notes in general:
- hardware: Dell E6330, amd64, 4 cores i5-3360M, 8 GByte RAM, 250 GByte SSD w/ 
TRIM
- WLAN: urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R
- kernel: GENERIC r302904 (July 15)
- poudriere 3.2-pre: compiling ~1800 ports in 4 builders
- swap as plain file in /usr/swap01, 8 GByte
- apart of the crashes below, no crash during buildworld, buildkernel and
  ~48 hours of poudriere fetching distfiles and making ~1800 ports
- no errors on 'memtest 1G'

crashes/observations:

16.07.2016 07:12 
- on shutdown swap device (plain file in /usr) could not be detached
- drop to kdb
- nothing in /var/log/messages

17.07.2016 19:41
- hard locked, had to power-off
- last command issued on console (no X11): cp -p * /usr/PKGDIR (around 1700 
files, 2 GByte)
- nothing in /var/log/messages

20.07.2016 19:27
- hard locked, had to power-off
- last command issued in xterm: fgrep mra... ~/*
- nothing in /var/log/messages

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Wer übersieht, dass wir uns den anderen weggenommen haben und sie uns 
wiederhaben wollen,
kann von den Kämpfen der letzten Tage keinen verstehen. Und kann natürlich auch 
keinen
dieser Kämpfe bestehen." Hermann Kant in jW 1.10.1989
___
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: memstick && Invalid partition table

2016-06-07 Thread Matthias Apitz
El día Tuesday, June 07, 2016 a las 09:15:03AM -0400, Allan Jude escribió:

> > If I use the fine memstick on some other laptop, in this case a Dell
> > Latitude E6330, it just says 'Invalid partition table!'
> > 
> > What could be wrong with it?
> > 
> > matthias
> > 
> 
> To fix the partition table to be the size of your memstick do:
> 
> gpart recover da0

this gave 'da0 recovering is not needed'

> 
> 
> If this does not work, try this (specific to some models of Dell
> Latitude and some HPs):
> 
> gpart set -a active da0

this worked, partition is now 'flag 80 (active)' and the stick boots
fine;

thanks for your help;

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Die Verkaufsschlager des Buchmarkts geben Auskunft über den Zustand einer 
Gesellschaft bzw.
sind, was diese Zeiten angeht, Gradmesser fortschreitenden Schwachsinns. ..." 
(jW 19.05.2016)
___
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"

memstick && Invalid partition table

2016-06-07 Thread Matthias Apitz

Hello,

To move a compiled system and kernel to other, smaller device I produce
so called memsticks which are made with the script
/usr/src/release/amd64/make-memstick.sh

They do, i.e. booting fine and showing for example on a netbook Acer C720 in
/var/log/messages on attach:

Jun  7 10:35:43 c720-r292778-amd64 kernel: da0 at umass-sim0 bus 0 scbus1 
target 0 lun 0
Jun  7 10:35:43 c720-r292778-amd64 kernel: da0:  
Removable Direct Access SCSI-2 device
Jun  7 10:35:43 c720-r292778-amd64 kernel: da0: Serial Number 0902213131
Jun  7 10:35:43 c720-r292778-amd64 kernel: da0: 40.000MB/s transfers
Jun  7 10:35:43 c720-r292778-amd64 kernel: da0: 7712MB (15794176 512 byte 
sectors)
Jun  7 10:35:43 c720-r292778-amd64 kernel: da0: quirks=0x2

wnd with FDISK:

$ fdisk da0
*** Working on device /dev/da0 ***
parameters extracted from in-core disklabel are:
cylinders=983 heads=255 sectors/track=63 (16065 blks/cyl)

parameters to be used for BIOS calculations are:
cylinders=983 heads=255 sectors/track=63 (16065 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 238 (0xee),(EFI GPT)
start 1, size 14683749 (7169 Meg), flag 0
beg: cyl 0/ head 0/ sector 2;
end: cyl 1023/ head 255/ sector 63
The data for partition 2 is:

The data for partition 3 is:

The data for partition 4 is:



If I use the fine memstick on some other laptop, in this case a Dell
Latitude E6330, it just says 'Invalid partition table!'

What could be wrong with it?

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Die Verkaufsschlager des Buchmarkts geben Auskunft über den Zustand einer 
Gesellschaft bzw.
sind, was diese Zeiten angeht, Gradmesser fortschreitenden Schwachsinns. ..." 
(jW 19.05.2016)
___
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: r300951: mountroot: waiting for device /dev/ad4s1a...

2016-06-04 Thread Matthias Apitz
El día Saturday, June 04, 2016 a las 02:41:48PM +0200, Michael Gmelin escribió:

> It's also covered in UPDATING:
> 
> 20151011:
> Compatibility shims for legacy ATA device names have been
> removed. It includes ATA_STATIC_ID kernel option,
> kern.cam.ada.legacy_aliases and kern.geom.raid.legacy_aliases
> loader tunables, kern.devalias.* environment variables, /dev/ad*
> and /dev/ar* symbolic links.
> 

Next time I will do read UPDATING. Thanks for your help.

    matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Die Verkaufsschlager des Buchmarkts geben Auskunft über den Zustand einer 
Gesellschaft bzw.
sind, was diese Zeiten angeht, Gradmesser fortschreitenden Schwachsinns. ..." 
(jW 19.05.2016)
___
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: r300951: mountroot: waiting for device /dev/ad4s1a...

2016-06-04 Thread Matthias Apitz
El día Saturday, June 04, 2016 a las 01:54:30PM +0200, Michael Gmelin escribió:

> 
> On Sat, 4 Jun 2016 13:48:52 +0200
> Matthias Apitz <g...@unixarea.de> wrote:
> 
> > > Did you do a full clean build?
> > > GENERIC or custom kernel config?  
> > 
> > yes, clean 'make buildkernel KERNCONF=GENERIC'
> And then 'make installkernel KERNCONF=GENERIC' I suppose.

yes, ofc :-)

> > interestingly: I can type at the prompt 'mountroot> ' into the dark
> > and always when I press Ctrl the chars are written to the screen and
> > so I can specify 'ufs:/dev/ad4s1a' which than leads to the same error
> > 19.
> 
> Did you try ufs:/dev/ada0s1a?

no, but now and it worked; I will adjust /etc/fstab; but why is this?

Thanks

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Die Verkaufsschlager des Buchmarkts geben Auskunft über den Zustand einer 
Gesellschaft bzw.
sind, was diese Zeiten angeht, Gradmesser fortschreitenden Schwachsinns. ..." 
(jW 19.05.2016)
___
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: r300951: mountroot: waiting for device /dev/ad4s1a...

2016-06-04 Thread Matthias Apitz

Hi Michael,

El día Saturday, June 04, 2016 a las 01:40:46PM +0200, Michael Gmelin escribió:

> Hi Matthias,
> 
> Did you try to connect an external USB keyboard?

no; it uses the laptop onboard keyboard;

> i386 or amd64?

i386;

> Did you do a full clean build?
> GENERIC or custom kernel config?

yes, clean 'make buildkernel KERNCONF=GENERIC'

interestingly: I can type at the prompt 'mountroot> ' into the dark and
always when I press Ctrl the chars are written to the screen and so I can
specify 'ufs:/dev/ad4s1a' which than leads to the same error 19.

I can as well boot an USB key with the old kernel r269739, mount
/dev/ad4s1a to /mnt, all fine; I did even a fsck while booted from USB
on /dev/ad4s1a. The FS is clean.

    matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Die Verkaufsschlager des Buchmarkts geben Auskunft über den Zustand einer 
Gesellschaft bzw.
sind, was diese Zeiten angeht, Gradmesser fortschreitenden Schwachsinns. ..." 
(jW 19.05.2016)
___
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: r300951: mountroot: waiting for device /dev/ad4s1a...

2016-06-04 Thread Matthias Apitz
El día Saturday, June 04, 2016 a las 12:18:26PM +0200, Matthias Apitz escribió:

> 
> Hello,
> 
> I'm trying to update my laptop Acer Aspire One D250 from r269739 to
> r300951. After 'make installkernel' it hangs for ever on reboot, waiting
> for the device /dev/ad4s1a. The old kernel boots fine.

short before mounting root are two error messages:

taskqgroup_adjust failed cnt: 1 stride: 1 mp_ncpus: 1 smp_started: 0
taskqgroup_adjust failed cnt: 1 stride: 1 mp_ncpus: 1 smp_started: 0
Timecounter "TSC" frequency 1596219540 Hz quality 1000
Trying to mount root drom ufs:/dev/ad4s1a [rw]...
mountroot: waiting for device /dev/ad4s1a ...
Mounting from ufs:/dev/ad4s1a failed with error 19.

Than it goes into the manual dialog to specify the root device but at
the prompt 

mountroot>

the kernel does not echo any typed chars;

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Die Verkaufsschlager des Buchmarkts geben Auskunft über den Zustand einer 
Gesellschaft bzw.
sind, was diese Zeiten angeht, Gradmesser fortschreitenden Schwachsinns. ..." 
(jW 19.05.2016)
___
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"

r300951: mountroot: waiting for device /dev/ad4s1a...

2016-06-04 Thread Matthias Apitz

Hello,

I'm trying to update my laptop Acer Aspire One D250 from r269739 to
r300951. After 'make installkernel' it hangs for ever on reboot, waiting
for the device /dev/ad4s1a. The old kernel boots fine.

What can I do?
Thx

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Die Verkaufsschlager des Buchmarkts geben Auskunft über den Zustand einer 
Gesellschaft bzw.
sind, was diese Zeiten angeht, Gradmesser fortschreitenden Schwachsinns. ..." 
(jW 19.05.2016)
___
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: r300951 make buildworld duration 18h

2016-05-30 Thread Matthias Apitz
El lunes, 30 de mayo de 2016 17:11:15 (CEST), Bob Bishop <r...@gid.co.uk> 
escribió:

HI,


On 30 May 2016, at 15:37, Matthias Apitz <g...@unixarea.de> wrote:


Hello,

Yesterday I pulled via svn co ... a fresh r300951 and started 
the buildworld as


# make -j2 buildworld

it ended today at lunchtime after 18 hours. The laptop has 2x 
Intel Atom 1.6GHz
and 1 GByte RAM and was otherwise unused. Is this the normal 
buildworld time of

today? I think it spent most of the time in building the llvm…


With 1GB it probably spent a lot of its time swapping.



the 'make -j2 buildkernel KERNCONF=GENERIC' lasted only 2:40h

matthias



--
Sent from my Ubuntu tablet
http://www.unixarea.de/
___
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"

r300951 make buildworld duration 18h

2016-05-30 Thread Matthias Apitz

Hello,

Yesterday I pulled via svn co ... a fresh r300951 and started the buildworld as

# make -j2 buildworld

it ended today at lunchtime after 18 hours. The laptop has 2x Intel Atom 1.6GHz
and 1 GByte RAM and was otherwise unused. Is this the normal buildworld time of
today? I think it spent most of the time in building the llvm...

Thx

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Die Verkaufsschlager des Buchmarkts geben Auskunft über den Zustand einer 
Gesellschaft bzw.
sind, was diese Zeiten angeht, Gradmesser fortschreitenden Schwachsinns. ..." 
(jW 19.05.2016)
___
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: LibreOffice and CUPS

2016-05-15 Thread Matthias Apitz
El día Sunday, May 15, 2016 a las 10:34:08AM -0700, Kevin Oberman escribió:

> cups and foomatic seem to have had some refactoring.
>  I had to delete foomatic-filters to upgrade cups-filters and then
> re-install it.I then realized that hplip no longer required
> foomatic-filters, so I simply deleted it. I assume that the required
> filters moved from one port to the other as the printer still works fine.
> (Note that this was cups-filters and not the base print/cups port.)

Please note that the OP said he only updated kernel and world and not the
ports (I know that there is some issue updating the older cups-* ports
to now only one cups port, but this is not the case here).

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
8 мая 1945: Спасибо, Советского Союза!  --  May 8, 1945: Thank you, Soviet 
Union! 
___
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: LibreOffice and CUPS

2016-05-14 Thread Matthias Apitz
El día Saturday, May 14, 2016 a las 12:27:28PM -0600, Sergey Manucharian 
escribió:

> After recent system update (I'm on FreeBSD 11.0-CURRENT r298793)
> LibreOffice doesn't see CUPS printers. It shows only "Generic printer",
> but doesn't actually print anything.

Libreoffice and cups are ports or packages made from ports, what are the 
versions of
them or your overall ports tree? And what do you mean by 'after recent
update', have you just updated kernel and world? 

    matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
8 мая 1945: Спасибо, Советского Союза!  --  May 8, 1945: Thank you, Soviet 
Union! 
___
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: Acer C720 crash at boot

2016-04-09 Thread Matthias Apitz
El día Saturday, April 09, 2016 a las 02:10:04PM +0200, Wolfgang Zenker 
escribió:

> Hi,
> 
> I can no longer boot my Acer C720 with current; during boot I get
> a panic and the system drops into kdb, unfortunately without a
> working keyboard. What is visible on the screen looks like
> it might be a stack trace; top line starts with vpanic().
> Would transcribing the screen output be of any use?
> ...

Hi,
Maybe a photo of the screen (put it on some server, not by mail, or send
it to me directly and I put it on my server).

matthias (long time C720 user with CURRENT)
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
___
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: continuous stream of writes?

2016-03-01 Thread Matthias Apitz
El día Tuesday, March 01, 2016 a las 08:50:05AM -0600, Eric van Gyzen escribió:

> >> The I/O mode of "top" might be useful:
> >>
> >> top -m io
> > 
> > Well that's different .. KDE konsole .. why on earth .. ?
> 
> Now try ktrace, fstat, and procstat.  See the man pages for usage.

Or as well truss to see on syscall level what the proc is doing/writing;

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
___
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: making editors/openoffice-devel within poudriere: out of swap with 10 GByte

2016-02-09 Thread Matthias Apitz
El día Monday, February 08, 2016 a las 04:08:50PM -0500, Allan Jude escribió:

> On 2016-02-08 15:38, Matthias Apitz wrote:
> >
> > Hello,
> >
> > I have a poudriere oven, amd64 based on r292778 and poudriere 
> > 3.1.99.20151204
> > which served fine to build some 1700 ports. Yesterday I started to make
> > in addition editors/openoffice-devel, and it ended up eating all
> > attached swap space and at the end today with out of swap after some ~15 
> > hours...
> >
> > The swap is 4 GByte /dev/ada0p3 and in addition 6 plain files of 1 GByte 
> > added
> > as swap devices.
> >
> > What I do not understand, while watching the situation with top, there
> > have only be running as maximum 2 processes clang++, and always starting new
> > processes for new foo.cxx files, and theses have had a memory of some
> > let's says 200 Mbytes each, as max. How can this lead to eat up 10 GByte 
> > swap
> > space?
> >
> > matthias
> >
> 
> Where you using the tmpfs feature of poudriere? I believe it is on by 
> default. This will obviously use up a bunch of ram and cause swapping.

Thanks. I commented out

# USE_TMPFS=

and now the picture in top is as expected. Used swap isn't growing after
2++ hours:

last pid: 39826;  load averages:  1.11,  1.08,  1.03 up 0+02:20:00  15:38:12
41 processes:  2 running, 39 sleeping
CPU: 47.0% user,  0.0% nice,  4.7% system,  0.0% interrupt, 48.2% idle
Mem: 106M Active, 2867M Inact, 679M Wired, 340M Buf, 220M Free
Swap: 3979M Total, 11M Used, 3968M Free

  PID USERNAMETHR PRI NICE   SIZERES STATE   C   TIMEWCPU COMMAND
39773 root  1  780   128M   107M CPU00   0:02  98.28% clang++
  867 guru  1  200 82872K  3772K select  1   0:02   0.01% sshd
32359 root  1  200 20096K  3300K CPU11   0:00   0.04% top
 1070 root  1  520  8404K  2848K wait0   0:26   0.35% sh
  296 root  1  200 20472K  2108K select  1   0:00   0.00% 
wpa_supplicant
39826 root  1  520  6220K  1424K nanslp  0   0:00   0.04% sleep
  752 root  1  200 10412K  1228K select  1   0:00   0.00% powerd

Watching with tail -f the log file, it seems even, that clang++ is compiling 
faster than before.

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5
___
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"

making editors/openoffice-devel within poudriere: out of swap with 10 GByte

2016-02-08 Thread Matthias Apitz

Hello,

I have a poudriere oven, amd64 based on r292778 and poudriere 3.1.99.20151204
which served fine to build some 1700 ports. Yesterday I started to make
in addition editors/openoffice-devel, and it ended up eating all
attached swap space and at the end today with out of swap after some ~15 
hours...

The swap is 4 GByte /dev/ada0p3 and in addition 6 plain files of 1 GByte added
as swap devices.

What I do not understand, while watching the situation with top, there
have only be running as maximum 2 processes clang++, and always starting new
processes for new foo.cxx files, and theses have had a memory of some
let's says 200 Mbytes each, as max. How can this lead to eat up 10 GByte swap
space?

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5
___
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"

libreoffice 5.x && problem with threads?

2016-02-04 Thread Matthias Apitz
  0x000800a8f280 in ?? () from 
/usr/local/lib/libreoffice/program/libsofficeapp.so
#4  0x000806012551 in DeInitVCL () from 
/usr/local/lib/libreoffice/program/libvcllo.so
#5  0x000806011e7b in VclResId () from 
/usr/local/lib/libreoffice/program/libvcllo.so
#6  0x000806012978 in SVMain () from 
/usr/local/lib/libreoffice/program/libvcllo.so
#7  0x000800abc91e in soffice_main () from 
/usr/local/lib/libreoffice/program/libsofficeapp.so
#8  0x00400870 in ?? ()
#9  0x0040077f in ?? ()
#10 0x000800621000 in ?? ()
#11 0x in ?? ()

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5
___
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"

after update to r292778 no interface ath0 and wlan0

2016-01-06 Thread Matthias Apitz
turned 0
ath0: [HT] enabling HT modes
ath0: [HT] enabling short-GI in 20MHz mode
ath0: [HT] 1 stream STBC receive enabled
ath0: [HT] 1 stream STBC transmit enabled
ath0: [HT] 2 RX streams; 2 TX streams
ath0: AR9460 mac 640.2 RF5110 phy 48.10
ath0: 2GHz radio: 0x; 5GHz radio: 0x
ehci0:  mem 0xe051f800-0xe051fbff 
at device 29.0 on pci0
usbus1: EHCI version 1.0
usbus1 on ehci0
isab0:  at device 31.0 on pci0
isa0:  on isab0
ahci0:  port 
0x1860-0x1867,0x1870-0x1873,0x1868-0x186f,0x1874-0x1877,0x1840-0x185f mem 
0xe051f000-0xe051f7ff irq 22 at device 31.2 on pci0
ahci0: AHCI v1.30 with 2 6Gbps ports, Port Multiplier not supported
ahcich0:  at channel 0 on ahci0
acpi_tz0:  on acpi0
acpi_acad0:  on acpi0
battery0:  on acpi0
atkbdc0:  port 0x60,0x64 irq 1 on acpi0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
ppc0: cannot reserve I/O port range
coretemp0:  on cpu0
est0:  on cpu0
coretemp1:  on cpu1
est1:  on cpu1
Timecounters tick every 1.000 msec
IPsec: Initialized Security Association Processing.
IP Filter: v5.1.2 initialized.  Default = pass all, Logging = enabled
hdacc0:  at cad 0 on hdac0
hdaa0:  at nid 1 on hdacc0
pcm0:  at nid 3 on hdaa0
smbus0:  on ig4iic0
usbus0: 5.0Gbps Super Speed USB v3.0
usbus1: 480Mbps High Speed USB v2.0
ugen0.1: <0x8086> at usbus0
uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
ugen1.1:  at usbus1
uhub1:  on usbus1
uhub0: 13 ports with 13 removable, self powered
uhub1: 2 ports with 2 removable, self powered
ugen0.2:  at usbus0
ugen1.2:  at usbus1
uhub2:  on 
usbus1
cyapa0:  at addr 0x67 on smbus0
cyapa0: cyapa init status 8b
cyapa0: CYTRA-103006-00 buttons=LM- res=870x470
smbus1:  on ig4iic1
uhub2: 8 ports with 8 removable, self powered
isl0:  at addr 0x44 on smbus1
hdacc1:  at cad 0 on hdac1
hdaa1:  at nid 1 on hdacc1
pcm1:  at nid 20,33 and 25,26 on hdaa1
usbd_setup_device_desc: getting device descriptor at addr 2 failed, 
USB_ERR_TIMEOUT
usbd_setup_device_desc: getting device descriptor at addr 2 failed, 
USB_ERR_TIMEOUT
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0:  ACS-2 ATA SATA 3.x device
ada0: Serial Number B862500493
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 1024bytes)
ada0: Command Queueing enabled
ada0: 122104MB (250069680 512 byte sectors)
SMP: AP CPU #1 Launched!
Timecounter "TSC" frequency 1396796212 Hz quality 1000
WARNING: WITNESS option enabled, expect reduced performance.
Trying to mount root from ufs:/dev/ada0p2 [rw,noatime]...
usbd_setup_device_desc: getting device descriptor at addr 2 failed, 
USB_ERR_TIMEOUT
usbd_setup_device_desc: getting device descriptor at addr 2 failed, 
USB_ERR_TIMEOUT
usbd_setup_device_desc: getting device descriptor at addr 2 failed, 
USB_ERR_TIMEOUT
ugen0.3:  at usbus0 (disconnected)
uhub_reattach_port: could not allocate new device
ugen0.3:  at usbus0
umass0:  on usbus0
umass0:  SCSI over Bulk-Only; quirks = 0x4101
umass0:1:0: Attached to scbus1
da0 at umass-sim0 bus 0 scbus1 target 0 lun 0
da0:  Removable Direct Access SPC-2 SCSI device
da0: Serial Number F82AEC82
da0: 40.000MB/s transfers
da0: 960MB (1966080 512 byte sectors)
da0: quirks=0x2
GEOM_ELI: Device da0.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI: Crypto: software

-- 
Matthias Apitz, ✉ g...@unixarea.de,  http://www.unixarea.de/  ☎ 
+49-176-38902045
___
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: after update to r292778 no interface ath0 and wlan0

2016-01-06 Thread Matthias Apitz
El día Thursday, January 07, 2016 a las 03:04:24AM +0100, Michael Gmelin 
escribió:

> > On 07 Jan 2016, at 02:49, Matthias Apitz <g...@unixarea.de> wrote:
> > 
> > 
> > Hello,
> > 
> > I have updated my Acer C720 netbook (amd64) from r285885 to r292778 and
> > now I do not see any network devices; the kernel is just GENERIC;
> > 
> > the lines in /etc/rc.conf are
> > 
> > wlans_ath0="wlan0"
> > ifconfig_wlan0="WPA DHCP"
> > 
> > (i.e. unchanged as they worked before); in dmesg the aht0 is shown as
> > usual with:
> > 
> 
> See https://lists.freebsd.org/pipermail/freebsd-net/2015-August/042976.html 
> and don't forget to run mergemaster to update rc scripts.
> 

I run in fact mermaster after installworld, but with flag -a; I have now moved 
from the
temproot:

# cd /var/tmp/temproot.*/etc/rc.d
# mv * /etc/rc.d
# cd ..
# rm group motd
# for i in *; do test -f $i && mv $i /etc ; done

and the network is fine again; thanks for the fast help;

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de,  http://www.unixarea.de/  ☎ 
+49-176-38902045
___
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: poudriere ports -c ... checks out the base system instead of the ports

2015-12-31 Thread Matthias Apitz
El día Wednesday, December 30, 2015 a las 03:39:11PM +0100, Matthias Apitz 
escribió:

> > # pkg info
> > dialog4ports-0.1.5_2   Console Interface to configure ports
> > pkg-1.6.2  Package manager
> > poudriere-devel-3.1.99.20151204 Port build and test system
> > 
> > # uname -a
> > FreeBSD poudriere-amd64 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r292778:
> > Mon Dec 28 05:45:37 CET 2015
> > root@poudriere-amd64:/usr/local/r292778/obj/usr/local/r292778/src/sys/GENERIC
> > amd64
> > 
> > When I now want to creat the ports it does not checkout the ports tree, but
> > the base system:
> 
> yep, even the 'ps ax' shows this:
> 
> 1201  0  S+0:00.02 sh /usr/local/share/poudriere/ports.sh -c -v -p 
> ports-20151230 -m svn+http
> 1237  0  S+0:00.08 /usr/bin/svnlite co http://svn.freebsd.org/base/head 
> /usr/local/poudriere/po
> 1200  1  Ss0:00.00 -sh (sh)
> 1238  1  R+0:00.00 ps ax
> 
> I can it make working with the options -m svn -U svn://svn.freebsd.org/ports/

I have had a look into the script /usr/local/share/poudriere/ports.sh
which does the work for creating(...) ports. I has a new option:

Options:
-U url-- URL where to fetch the ports tree from.

All is working fine now and the only which remains is updating the man
page of poudriere for this.

Thanks

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de,  http://www.unixarea.de/  ☎ 
+49-176-38902045
___
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: Can't install 11 .iso images in virtual box

2015-12-29 Thread Matthias Apitz

On Tuesday, 29 December 2015 17:01:28 CET, Glen Barber wrote:

On Tue, Dec 29, 2015 at 07:57:42AM -0800, Yuri wrote:

disk1.iso has kernel panic during boot.

And bootonly.iso boots but after downloading kernel and base it says that
there is the incorrect checksum, and it needs to downlodagain.

Just tried FreeBSD-11.0-CURRENT-amd64-20151217-r292413-disc1.iso



This is because we can only store (currently) one version of the
distribution sets on FTP, and the most recent build (from last night) is
syncing to the mirrors currently.

What was the panic message for disc1.iso?  I do not recall seeing
a panic with that image when I tested the last set of builds.

Glen




I had the same problem yesterday and got a reply that this is a known bug, 
check the archive of the list:


matthias


--
Sent from my Ubuntu phone
http://www.unixarea.de/
___
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"


interrupt and resume poudriere jail creation

2015-12-29 Thread Matthias Apitz

Hello,

I'm creating a new -CURRENT jail for poudriere with:

# poudriere jail -c -j freebsd-r292778 -m svn+http -v head@r292778

The src/ is checked out via SVN and it is already compiling the jail
for two hours, but I have to interrupt it for some network problem here
and I did the mistake to start it in a SSH session :-(

Is there a way like -DNO_CLEAN when compiling 'make buildkernel' to
resume the compilation in the jail at the point of the interrupt?

Thanks

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de,  http://www.unixarea.de/  ☎ 
+49-176-38902045
___
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"

panic while booting the official ISO 11-CUR-amd64-20151217-r292413

2015-12-28 Thread Matthias Apitz

Hello,

I downloaded the ISO for the above version and when I boot it in a
VMWare it panics reproduceable after trying to mount the root; see the
message captured in the last screens:

http://www.unixarea.de/panic-01.jpg
http://www.unixarea.de/panic-02.jpg

Any comments or hints?

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de,  http://www.unixarea.de/  ☎ 
+49-176-38902045
___
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: panic while booting the official ISO 11-CUR-amd64-20151217-r292413

2015-12-28 Thread Matthias Apitz
El día Monday, December 28, 2015 a las 02:12:29PM +0100, Matthias Apitz 
escribió:

> 
> Hello,
> 
> I downloaded the ISO for the above version and when I boot it in a
> VMWare it panics reproduceable after trying to mount the root; see the
> message captured in the last screens:
> 
> http://www.unixarea.de/panic-01.jpg
> http://www.unixarea.de/panic-02.jpg
> 
> Any comments or hints?

The downloaded VMWare image .vmdk of the same revision r292413 boots
fine;

    matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de,  http://www.unixarea.de/  ☎ 
+49-176-38902045
___
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"

  1   2   3   >