Re: rpi-b leds
On Tue, Aug 23, 2016 at 1:00 AM, Luiz Otavio O Souza wrote: > On 22 August 2016 at 08:55, Andrey Fesenko wrote: >> On Mon, Aug 22, 2016 at 1:29 PM, Daniel Braniss wrote: >>> Hi, >>> I see that now both leds on the rpi-2 are operational, >>> any chance it can happen on the rpi-b too? >>> >> >> A year or two ago, rpi-b had operational leds, it's make not working >> after rework fdt/std layer > > I tested the leds on two different rpi-b and the leds are working. > Maybe you are talking about the b+ model ? > > The ACT or OK led for the old boards (< b+) are wired to gpio 16. The > b+ has two leds, they are wired to pins 47 and 35. > > For a quick fix, edit your dts and the leds will work. > > Can you check the board revision for your rpi ? (sysctl hw.board.revision) > > These are the ones I tested: > > hw.board.revision: 3 > hw.board.revision: 14 > > Tested with r301978. > > Luiz Sorry for misinformation Raspberry Pi Model B (Rev 2.0, 512Mb): hw.board.revision: 15 leds work after complete boot ___ 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: kern.proc.pathname failure while booting from zfs
Le 20 août 2016 22:03, "Frederic Chardon" a
écrit :
>
> Hi
>
> I see a strange interaction between zfs on root and kern.proc.pathname
> on my laptop. Whenever I try to use gcore it fails with:
> gcore 1023
> gcore: kern.proc.pathname failure
>
> However, gcore /usr/local/bin/zsh 1023 is working properly.
>
> I made some tests booting from usb stick (fresh installworld, no
> src.conf, no make.conf, GENERIC kernel)
> What works: having / on ufs and importing a zfs pool later on.
> What doesn't: having / on zfs, whatever the settings for checksum,
> compression, or normalization.
>
> Both 11-stable and 12-current behave this way. Current from may-june
> worked properly.
> adb, chromium and virtualbox as well stopped working at approximately
> the same time, however I don't know if it is linked ("truss -f adb
> start-server" shows that garbage is passed to execl after forking).
>
> Any idea what's going on? Does anybody else see this?
>
> Thanks!
Nobody else have this problem? I reinstalled the system from scratch and
still gcore fails with the same error, even in single user mode.
___
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: kern.proc.pathname failure while booting from zfs
On Tue, Aug 23, 2016 at 09:27:56AM +0200, Frederic Chardon wrote:
> Le 20 ao??t 2016 22:03, "Frederic Chardon" a
> ??crit :
> >
> > Hi
> >
> > I see a strange interaction between zfs on root and kern.proc.pathname
> > on my laptop. Whenever I try to use gcore it fails with:
> > gcore 1023
> > gcore: kern.proc.pathname failure
> >
> > However, gcore /usr/local/bin/zsh 1023 is working properly.
> >
> > I made some tests booting from usb stick (fresh installworld, no
> > src.conf, no make.conf, GENERIC kernel)
> > What works: having / on ufs and importing a zfs pool later on.
> > What doesn't: having / on zfs, whatever the settings for checksum,
> > compression, or normalization.
> >
> > Both 11-stable and 12-current behave this way. Current from may-june
> > worked properly.
> > adb, chromium and virtualbox as well stopped working at approximately
> > the same time, however I don't know if it is linked ("truss -f adb
> > start-server" shows that garbage is passed to execl after forking).
> >
> > Any idea what's going on? Does anybody else see this?
> >
> > Thanks!
>
> Nobody else have this problem? I reinstalled the system from scratch and
> still gcore fails with the same error, even in single user mode.
Do you have a property on your root fs which forces it to ignore case in
the file names ?
___
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: Somethign missing in my environment?
On 22-8-2016 17:02, Willem Jan Withagen wrote: > Giving it a last retry building over NFS mounts. > > Which sort of worked after I exclude some boot code that nagged me about > things growing to big. Which I attributed to "-g -O0". > But then I was able to complete buildword and buildkernel. > > So sort of happy. Now I need to find out why the reboot did not work. > But that requires me next to the box. Right, Building/installing over NFS worked. And then I shot myself in the foot. Due to '-g -O0' the bootsector stuff got too big. So I commented out that part of the Makefile, during build. And ran install, which installed wrong/corrupt files in /boot, and I got stuck in BTX. :( But after some repairing with a boot-stick, and some ZFS voodoo, I installed correct bootloaders. And things are humming away. --WjW ___ 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"
major code change for .zfs
Please review and test a change to .zfs code that is intended to make the code aligned with FreeBSD VFS and, as such, more stable: https://reviews.freebsd.org/D7421 The change removes two features. .zfs/shares is gone because it was unused on FreeBSD anyway. We can restore that when we need it. An ability to take a snapshot by creating a directory under .zfs/snapshot is removed. I hope that you didn't use it. Please do not start using it now :-) Again, this feature can be restored with some work. The reason I removed it is that its companion features of destroying and renaming snapshots were already missing on FreeBSD, and properly implementing the feature required some more work. -- Andriy Gapon ___ 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"
Going to 11-STABLE
Hello all. I'm using an old 11-CURRENT (FreeBSD 11.0-CURRENT #2 r293335) and with the relase date for 11 getting closer, I'd like to go to 11-STABLE. I had the "URL: svn://svn.freebsd.org/base/head" under /usr/src and switched to "URL: svn://svn.freebsd.org/base/stable/11". Is this the right way to go (after the svn ends, i'll make buildworld, make buildkernel, and so on)? Just to be sure... Thanks in advance, -- Ricardo Campos Passanezi ___ 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: Going to 11-STABLE
> On Aug 23, 2016, at 11:30, Ricardo Campos Passanezi > wrote: > > Hello all. > > I'm using an old 11-CURRENT (FreeBSD 11.0-CURRENT #2 r293335) and with > the relase date for 11 getting closer, I'd like to go to 11-STABLE. > > I had the "URL: svn://svn.freebsd.org/base/head" under /usr/src and > switched to "URL: svn://svn.freebsd.org/base/stable/11". > > Is this the right way to go (after the svn ends, i'll make buildworld, > make buildkernel, and so on)? Just to be sure... > > Thanks in advance, Yes, it’s correct -- Renato Botelho ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
FreeBSD 12 - subversion
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] --- subversion/libsvn_diff/libsvn_diff-1.la --- cd subversion/libsvn_diff && /bin/sh "/usr/ports/devel/subversion/work/subversion-1.9.4/libtool" --tag=CC --silent --mode=link cc -Werror=unknown-warning-option -O2 -pipe -fpic -DPIC -fstack-protector -fno-strict-aliasing -O2 -pipe -fpic -DPIC -fstack-protector -fno-strict-aliasing -fstack-protector -L/usr/local/lib -L/usr/local/lib/db5 -L/usr/local/lib -L/usr/local/lib -rpath /usr/local/lib -version-info 0 -o libsvn_diff-1.la binary_diff.lo deprecated.lo diff.lo diff3.lo diff4.lo diff_file.lo diff_memory.lo diff_tree.lo lcs.lo parse-diff.lo token.lo util.lo ../../subversion/libsvn_subr/libsvn_subr-1.la -L/usr/local/lib -laprutil-1 -L/usr/local/lib -lapr-1 -lz -lintl --- subversion/libsvn_fs_util/libsvn_fs_util-1.la --- cd subversion/libsvn_fs_util && /bin/sh "/usr/ports/devel/subversion/work/subversion-1.9.4/libtool" --tag=CC --silent --mode=link cc -Werror=unknown-warning-option -O2 -pipe -fpic -DPIC -fstack-protector -fno-strict-aliasing -O2 -pipe -fpic -DPIC -fstack-protector -fno-strict-aliasing -fstack-protector -L/usr/local/lib -L/usr/local/lib/db5 -L/usr/local/lib -L/usr/local/lib -rpath /usr/local/lib -version-info 0 -o libsvn_fs_util-1.la fs-util.lo ../../subversion/libsvn_subr/libsvn_subr-1.la -L/usr/local/lib -laprutil-1 -L/usr/local/lib -lapr-1 -lintl --- tools/dev/x509-parser --- cd tools/dev && /bin/sh "/usr/ports/devel/subversion/work/subversion-1.9.4/libtool" --tag=CC --silent --mode=link cc -Werror=unknown-warning-option -O2 -pipe -fpic -DPIC -fstack-protector -fno-strict-aliasing -O2 -pipe -fpic -DPIC -fstack-protector -fno-strict-aliasing -fstack-protector -L/usr/local/lib -L/usr/local/lib/db5 -L/usr/local/lib -L/usr/local/lib -rpath /usr/local/lib -o x509-parser x509-parser.lo ../../subversion/libsvn_subr/libsvn_subr-1.la -L/usr/local/lib -lapr-1 -lintl --- tools/dev/fsfs-access-map --- /usr/local/lib/libapr-1.so: undefined reference to `fdatasync@FBSD_1.5' cc: error: linker command failed with exit code 1 (use -v to see invocation) --- tools/dev/x509-parser --- /usr/local/lib/libapr-1.so: undefined reference to `fdatasync@FBSD_1.5' --- tools/dev/fsfs-access-map --- *** [tools/dev/fsfs-access-map] Error code 1 make[2]: stopped in /usr/ports/devel/subversion/work/subversion-1.9.4 --- tools/dev/x509-parser --- cc: error: linker command failed with exit code 1 (use -v to see invocation) *** [tools/dev/x509-parser] Error code 1 make[2]: stopped in /usr/ports/devel/subversion/work/subversion-1.9.4 2 errors make[2]: stopped in /usr/ports/devel/subversion/work/subversion-1.9.4 ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make[1]: stopped in /usr/ports/devel/subversion *** Error code 1 Stop. make: stopped in /usr/ports/devel/subversion ___ 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"
[solved] Re: FreeBSD 12 - subversion
Solved - i reinstall devel/apr1 On 23.08.2016 17:24, 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] > > --- subversion/libsvn_diff/libsvn_diff-1.la --- > cd subversion/libsvn_diff && /bin/sh > "/usr/ports/devel/subversion/work/subversion-1.9.4/libtool" --tag=CC > --silent --mode=link cc -Werror=unknown-warning-option -O2 -pipe -fpic > -DPIC -fstack-protector -fno-strict-aliasing -O2 -pipe -fpic -DPIC > -fstack-protector -fno-strict-aliasing -fstack-protector > -L/usr/local/lib -L/usr/local/lib/db5 -L/usr/local/lib > -L/usr/local/lib -rpath /usr/local/lib -version-info 0 -o > libsvn_diff-1.la binary_diff.lo deprecated.lo diff.lo diff3.lo diff4.lo > diff_file.lo diff_memory.lo diff_tree.lo lcs.lo parse-diff.lo token.lo > util.lo ../../subversion/libsvn_subr/libsvn_subr-1.la -L/usr/local/lib > -laprutil-1 -L/usr/local/lib -lapr-1 -lz -lintl > --- subversion/libsvn_fs_util/libsvn_fs_util-1.la --- > cd subversion/libsvn_fs_util && /bin/sh > "/usr/ports/devel/subversion/work/subversion-1.9.4/libtool" --tag=CC > --silent --mode=link cc -Werror=unknown-warning-option -O2 -pipe -fpic > -DPIC -fstack-protector -fno-strict-aliasing -O2 -pipe -fpic -DPIC > -fstack-protector -fno-strict-aliasing -fstack-protector > -L/usr/local/lib -L/usr/local/lib/db5 -L/usr/local/lib > -L/usr/local/lib -rpath /usr/local/lib -version-info 0 -o > libsvn_fs_util-1.la fs-util.lo > ../../subversion/libsvn_subr/libsvn_subr-1.la -L/usr/local/lib > -laprutil-1 -L/usr/local/lib -lapr-1 -lintl > --- tools/dev/x509-parser --- > cd tools/dev && /bin/sh > "/usr/ports/devel/subversion/work/subversion-1.9.4/libtool" --tag=CC > --silent --mode=link cc -Werror=unknown-warning-option -O2 -pipe -fpic > -DPIC -fstack-protector -fno-strict-aliasing -O2 -pipe -fpic -DPIC > -fstack-protector -fno-strict-aliasing -fstack-protector > -L/usr/local/lib -L/usr/local/lib/db5 -L/usr/local/lib > -L/usr/local/lib -rpath /usr/local/lib -o x509-parser x509-parser.lo > ../../subversion/libsvn_subr/libsvn_subr-1.la -L/usr/local/lib -lapr-1 > -lintl > --- tools/dev/fsfs-access-map --- > /usr/local/lib/libapr-1.so: undefined reference to `fdatasync@FBSD_1.5' > cc: error: linker command failed with exit code 1 (use -v to see invocation) > --- tools/dev/x509-parser --- > /usr/local/lib/libapr-1.so: undefined reference to `fdatasync@FBSD_1.5' > --- tools/dev/fsfs-access-map --- > *** [tools/dev/fsfs-access-map] Error code 1 > > make[2]: stopped in /usr/ports/devel/subversion/work/subversion-1.9.4 > --- tools/dev/x509-parser --- > cc: error: linker command failed with exit code 1 (use -v to see invocation) > *** [tools/dev/x509-parser] Error code 1 > > make[2]: stopped in /usr/ports/devel/subversion/work/subversion-1.9.4 > 2 errors > > make[2]: stopped in /usr/ports/devel/subversion/work/subversion-1.9.4 > ===> Compilation failed unexpectedly. > Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to > the maintainer. > *** Error code 1 > > Stop. > make[1]: stopped in /usr/ports/devel/subversion > *** Error code 1 > > Stop. > make: stopped in /usr/ports/devel/subversion > > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD 12 - subversion
Am Tue, 23 Aug 2016 17:24:07 +0200 Jochen Neumeister schrieb: > 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] > > --- subversion/libsvn_diff/libsvn_diff-1.la --- > cd subversion/libsvn_diff && /bin/sh > "/usr/ports/devel/subversion/work/subversion-1.9.4/libtool" --tag=CC > --silent --mode=link cc -Werror=unknown-warning-option -O2 -pipe -fpic > -DPIC -fstack-protector -fno-strict-aliasing -O2 -pipe -fpic -DPIC > -fstack-protector -fno-strict-aliasing -fstack-protector > -L/usr/local/lib -L/usr/local/lib/db5 -L/usr/local/lib > -L/usr/local/lib -rpath /usr/local/lib -version-info 0 -o > libsvn_diff-1.la binary_diff.lo deprecated.lo diff.lo diff3.lo diff4.lo > diff_file.lo diff_memory.lo diff_tree.lo lcs.lo parse-diff.lo token.lo > util.lo ../../subversion/libsvn_subr/libsvn_subr-1.la -L/usr/local/lib > -laprutil-1 -L/usr/local/lib -lapr-1 -lz -lintl > --- subversion/libsvn_fs_util/libsvn_fs_util-1.la --- > cd subversion/libsvn_fs_util && /bin/sh > "/usr/ports/devel/subversion/work/subversion-1.9.4/libtool" --tag=CC > --silent --mode=link cc -Werror=unknown-warning-option -O2 -pipe -fpic > -DPIC -fstack-protector -fno-strict-aliasing -O2 -pipe -fpic -DPIC > -fstack-protector -fno-strict-aliasing -fstack-protector > -L/usr/local/lib -L/usr/local/lib/db5 -L/usr/local/lib > -L/usr/local/lib -rpath /usr/local/lib -version-info 0 -o > libsvn_fs_util-1.la fs-util.lo > ../../subversion/libsvn_subr/libsvn_subr-1.la -L/usr/local/lib > -laprutil-1 -L/usr/local/lib -lapr-1 -lintl > --- tools/dev/x509-parser --- > cd tools/dev && /bin/sh > "/usr/ports/devel/subversion/work/subversion-1.9.4/libtool" --tag=CC > --silent --mode=link cc -Werror=unknown-warning-option -O2 -pipe -fpic > -DPIC -fstack-protector -fno-strict-aliasing -O2 -pipe -fpic -DPIC > -fstack-protector -fno-strict-aliasing -fstack-protector > -L/usr/local/lib -L/usr/local/lib/db5 -L/usr/local/lib > -L/usr/local/lib -rpath /usr/local/lib -o x509-parser x509-parser.lo > ../../subversion/libsvn_subr/libsvn_subr-1.la -L/usr/local/lib -lapr-1 > -lintl > --- tools/dev/fsfs-access-map --- > /usr/local/lib/libapr-1.so: undefined reference to `fdatasync@FBSD_1.5' > cc: error: linker command failed with exit code 1 (use -v to see invocation) > --- tools/dev/x509-parser --- > /usr/local/lib/libapr-1.so: undefined reference to `fdatasync@FBSD_1.5' > --- tools/dev/fsfs-access-map --- > *** [tools/dev/fsfs-access-map] Error code 1 > > make[2]: stopped in /usr/ports/devel/subversion/work/subversion-1.9.4 > --- tools/dev/x509-parser --- > cc: error: linker command failed with exit code 1 (use -v to see invocation) > *** [tools/dev/x509-parser] Error code 1 > > make[2]: stopped in /usr/ports/devel/subversion/work/subversion-1.9.4 > 2 errors > > make[2]: stopped in /usr/ports/devel/subversion/work/subversion-1.9.4 > ===> Compilation failed unexpectedly. > Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to > the maintainer. > *** Error code 1 > > Stop. > make[1]: stopped in /usr/ports/devel/subversion > *** Error code 1 > > Stop. > make: stopped in /usr/ports/devel/subversion > > ___ > 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" I see similar problems quite often on our experimental platforms, where we move forward in compiling the OS and ports perpetually. If I get a hint so clear like yours, I recompile the port the failing library belongs to. In your case, I guess it is: [ports] pkg which /usr/local/lib/libapr-1.so /usr/local/lib/libapr-1.so was installed by package apr-1.5.2.1.5.4_1 pkg which -o /usr/local/lib/libapr-1.so /usr/local/lib/libapr-1.so was installed by package devel/apr1 So, please try recompiling the port devel/apr1 (sometimes, if the port fails to compile, a "make -C devel/apr1 rmconfig clean" and then reinstalling helps (supoosed you're in /usr/ports already). Kind regards, O. Hartmann /usr/local/lib/libapr-1.so was installed by package apr-1.5.2.1.5.4_1 pgpeBUoRhBeZJ.pgp Description: OpenPGP digital signature
Re: FreeBSD 12 - subversion
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"
FreeBSD 11.0 RC1 kernel panic with iwm firmware
Hi all, just installed RC1 on my T540 Thinkpad. I installed some tools did a few reboots, then added the laptops wireless Intel 7260 firmware to /boot/loader.conf iwm7260fw_load="YES" if_iwm_load="YES" (think i put them i this order, shouldn't matter?) after a reboot unlocked my Geli and selected the default boot options. Next i see the usual text scrolling by, see a glimpse of iwm driver. Then Fatal trap 12: page fault while in kernel mode (with more info... ) then the machine reboots. Next tried single user mode and safe mode, with the same results. I managed to take a picture of the last lines before a reboot. I'll send a link to it in a minute. How to remove these kernel modules from a Geli encrypted harddisk? Or what other method should be used to correct the situation? I can re-install the machine, just trying to learn new tricks. Br, Tommi ___ 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 11.0 RC1 kernel panic with iwm firmware
Here is a link to the Fatal trap image http://imgur.com/gallery/NjoEF Br, Tommi On Aug 23, 2016 20:26, "Tommi Pernila" wrote: > > Hi all, > > just installed RC1 on my T540 Thinkpad. > I installed some tools did a few reboots, then added the laptops wireless Intel 7260 firmware to /boot/loader.conf > > iwm7260fw_load="YES" > if_iwm_load="YES" > > (think i put them i this order, shouldn't matter?) > > after a reboot unlocked my Geli and selected the default boot options. > > Next i see the usual text scrolling by, see a glimpse of iwm driver. > Then > > Fatal trap 12: page fault while in kernel mode > (with more info... ) > > then the machine reboots. > > Next tried single user mode and safe mode, with the same results. > > I managed to take a picture of the last lines before a reboot. > I'll send a link to it in a minute. > > > How to remove these kernel modules from a Geli encrypted harddisk? > > Or what other method should be used to correct the situation? > > I can re-install the machine, just trying to learn new tricks. > > Br, > > Tommi ___ 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: kern.proc.pathname failure while booting from zfs
2016-08-23 9:35 GMT+02:00 Konstantin Belousov :
> On Tue, Aug 23, 2016 at 09:27:56AM +0200, Frederic Chardon wrote:
>> Le 20 ao??t 2016 22:03, "Frederic Chardon" a
>> ??crit :
>> >
>> > Hi
>> >
>> > I see a strange interaction between zfs on root and kern.proc.pathname
>> > on my laptop. Whenever I try to use gcore it fails with:
>> > gcore 1023
>> > gcore: kern.proc.pathname failure
>> >
>> > However, gcore /usr/local/bin/zsh 1023 is working properly.
>> >
>> > I made some tests booting from usb stick (fresh installworld, no
>> > src.conf, no make.conf, GENERIC kernel)
>> > What works: having / on ufs and importing a zfs pool later on.
>> > What doesn't: having / on zfs, whatever the settings for checksum,
>> > compression, or normalization.
>> >
>> > Both 11-stable and 12-current behave this way. Current from may-june
>> > worked properly.
>> > adb, chromium and virtualbox as well stopped working at approximately
>> > the same time, however I don't know if it is linked ("truss -f adb
>> > start-server" shows that garbage is passed to execl after forking).
>> >
>> > Any idea what's going on? Does anybody else see this?
>> >
>> > Thanks!
>>
>> Nobody else have this problem? I reinstalled the system from scratch and
>> still gcore fails with the same error, even in single user mode.
>
> Do you have a property on your root fs which forces it to ignore case in
> the file names ?
No. I do have normalization set to formC though. I observed the same
behavior with the property unset (in fact, with no property set to
anything but default as well).
If I boot from usb stick and import the pool afterwards it works properly.
zpool get all zbase
NAME PROPERTY VALUE SOURCE
zbase size 9,94G -
zbase capacity 43%-
zbase altroot- default
zbase health ONLINE -
zbase guid 8964242380523899513default
zbase version- default
zbase bootfs zbase/bootenv/11-STABLElocal
zbase delegation on default
zbase autoreplaceoffdefault
zbase cachefile - default
zbase failmode wait default
zbase listsnapshots offdefault
zbase autoexpand offdefault
zbase dedupditto 0 default
zbase dedupratio 1.00x -
zbase free 5,65G -
zbase allocated 4,29G -
zbase readonly off-
zbase comment- default
zbase expandsize - -
zbase freeing0 default
zbase fragmentation 41%-
zbase leaked 0 default
zbase feature@async_destroy enabledlocal
zbase feature@empty_bpobjactive local
zbase feature@lz4_compress active local
zbase feature@multi_vdev_crash_dump enabledlocal
zbase feature@spacemap_histogram active local
zbase feature@enabled_txgactive local
zbase feature@hole_birth active local
zbase feature@extensible_dataset enabledlocal
zbase feature@embedded_data active local
zbase feature@bookmarks enabledlocal
zbase feature@filesystem_limits enabledlocal
zbase feature@large_blocks enabledlocal
zbase feature@sha512 enabledlocal
zbase feature@skein enabledlocal
zfs get all zbase/bootenv/11-STABLE
NAME PROPERTY VALUE SOURCE
zbase/bootenv/11-STABLE type filesystem-
zbase/bootenv/11-STABLE creation sam. août 20 13:07 2016 -
zbase/bootenv/11-STABLE used 4,23G -
zbase/bootenv/11-STABLE available 5,34G -
zbase/bootenv/11-STABLE referenced2,72G -
zb
Re: kern.proc.pathname failure while booting from zfs
2016-08-23 19:35 GMT+02:00 Frederic Chardon :
> 2016-08-23 9:35 GMT+02:00 Konstantin Belousov :
>> On Tue, Aug 23, 2016 at 09:27:56AM +0200, Frederic Chardon wrote:
>>> Le 20 ao??t 2016 22:03, "Frederic Chardon" a
>>> ??crit :
>>> >
>>> > Hi
>>> >
>>> > I see a strange interaction between zfs on root and kern.proc.pathname
>>> > on my laptop. Whenever I try to use gcore it fails with:
>>> > gcore 1023
>>> > gcore: kern.proc.pathname failure
>>> >
>>> > However, gcore /usr/local/bin/zsh 1023 is working properly.
>>> >
>>> > I made some tests booting from usb stick (fresh installworld, no
>>> > src.conf, no make.conf, GENERIC kernel)
>>> > What works: having / on ufs and importing a zfs pool later on.
>>> > What doesn't: having / on zfs, whatever the settings for checksum,
>>> > compression, or normalization.
>>> >
>>> > Both 11-stable and 12-current behave this way. Current from may-june
>>> > worked properly.
>>> > adb, chromium and virtualbox as well stopped working at approximately
>>> > the same time, however I don't know if it is linked ("truss -f adb
>>> > start-server" shows that garbage is passed to execl after forking).
>>> >
>>> > Any idea what's going on? Does anybody else see this?
>>> >
>>> > Thanks!
>>>
>>> Nobody else have this problem? I reinstalled the system from scratch and
>>> still gcore fails with the same error, even in single user mode.
>>
>> Do you have a property on your root fs which forces it to ignore case in
>> the file names ?
>
> No. I do have normalization set to formC though. I observed the same
> behavior with the property unset (in fact, with no property set to
> anything but default as well).
> If I boot from usb stick and import the pool afterwards it works properly.
>
> zpool get all zbase
> NAME PROPERTY VALUE SOURCE
> zbase size 9,94G -
> zbase capacity 43%-
> zbase altroot- default
> zbase health ONLINE -
> zbase guid 8964242380523899513default
> zbase version- default
> zbase bootfs zbase/bootenv/11-STABLElocal
> zbase delegation on default
> zbase autoreplaceoffdefault
> zbase cachefile - default
> zbase failmode wait default
> zbase listsnapshots offdefault
> zbase autoexpand offdefault
> zbase dedupditto 0 default
> zbase dedupratio 1.00x -
> zbase free 5,65G -
> zbase allocated 4,29G -
> zbase readonly off-
> zbase comment- default
> zbase expandsize - -
> zbase freeing0 default
> zbase fragmentation 41%-
> zbase leaked 0 default
> zbase feature@async_destroy enabledlocal
> zbase feature@empty_bpobjactive local
> zbase feature@lz4_compress active local
> zbase feature@multi_vdev_crash_dump enabledlocal
> zbase feature@spacemap_histogram active local
> zbase feature@enabled_txgactive local
> zbase feature@hole_birth active local
> zbase feature@extensible_dataset enabledlocal
> zbase feature@embedded_data active local
> zbase feature@bookmarks enabledlocal
> zbase feature@filesystem_limits enabledlocal
> zbase feature@large_blocks enabledlocal
> zbase feature@sha512 enabledlocal
> zbase feature@skein enabledlocal
>
>
> zfs get all zbase/bootenv/11-STABLE
> NAME PROPERTY VALUE
> SOURCE
> zbase/bootenv/11-STABLE type filesystem-
> zbase/bootenv/11-STABLE creation sam. août 20 13:07 2016 -
> zbase/bootenv/11-STABLE used
Re: FreeBSD 11.0 RC1 kernel panic with iwm firmware
On Tue, Aug 23, 2016 at 08:26:13PM +0300, Tommi Pernila wrote: > How to remove these kernel modules from a Geli encrypted harddisk? > > Or what other method should be used to correct the situation? > > I can re-install the machine, just trying to learn new tricks. > > Br, > > Tommi I've had a similar situation in the past. Here's what I remember doing: Escape to the loader prompt during boot, then use 'unload' to prevent it from loading those modules and 'boot -s' to bring the system up in single-user mode so you can edit loader.conf. signature.asc Description: PGP signature
FreeBSD 11 RC1 - no wifi
Hi, I have upgraded from FreeBSD 10.3 to 11 RC1 on my Lenovo W450 with Intel Centrino Ultimate-N 6300 After upgrade and a last reboot the iwn driver gets loaded but no iwn0 interface pops up. Doing a 'service netif restart' crashes the machine and a core is written. I have attached the output of the dmesg command. If somebody needs the core, I can upload it somewhere and give you the download link. Please tell me how I can help you guys. Cheers, Stefan tun0: link state changed to DOWN wlan0: link state changed to DOWN lagg0: link state changed to DOWN wlan0: link state changed to UP lagg0: link state changed to UP pid 97228 (wine), uid 1001: exited on signal 10 (core dumped) wlan0: link state changed to DOWN lagg0: link state changed to DOWN Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...0 0 0 0 0 0 done All buffers synced. Uptime: 10h16m41s GEOM_ELI: Device ada1p1.eli destroyed. GEOM_ELI: Detached ada1p1.eli on last close. Copyright (c) 1992-2016 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.3-RELEASE-p4 #0: Sat May 28 12:23:44 UTC 2016 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 CPU: Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz (2394.61-MHz K8-class CPU) Origin="GenuineIntel" Id=0x306a9 Family=0x6 Model=0x3a Stepping=9 Features=0xbfebfbff Features2=0x7fbae3bf AMD Features=0x28100800 AMD Features2=0x1 Structured Extended Features=0x281 XSAVE Features=0x1 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory = 34359738368 (32768 MB) avail memory = 32887021568 (31363 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 random: initialized ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 cryptosoft0: on motherboard aesni0: on motherboard acpi0: on motherboard acpi_ec0: port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 cpu4: on acpi0 cpu5: on acpi0 cpu6: on acpi0 cpu7: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 550 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0x5000-0x507f mem 0xf200-0xf2ff,0xe000-0xefff,0xf000-0xf1ff irq 16 at device 0.0 on pci1 nvidia0: on vgapci0 vgapci0: child nvidia0 requested pci_enable_io vgapci0: child nvidia0 requested pci_enable_io vgapci0: Boot video device hdac0: mem 0xf300-0xf3003fff irq 17 at device 0.1 on pci1 xhci0: mem 0xf532-0xf532 irq 16 at device 20.0 on pci0 xhci0: 32 bytes context size, 64-bit DMA xhci0: Port routing mask set to 0x usbus0 on xhci0 pci0: at device 22.0 (no driver attached) em0: port 0x6040-0x605f mem 0xf530-0xf531,0xf533b000-0xf533bfff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Ethernet address: 3c:97:0e:c3:c9:d0 ehci0: mem 0xf533a000-0xf533a3ff irq 16 at device 26.0 on pci0 usbus1: EHCI version 1.0 usbus1 on ehci0 hdac1: mem 0xf533-0xf5333fff irq 22 at device 27.0 on pci0 pcib2: irq 16 at device 28.0 on pci0 pci2: on pcib2 sdhci_pci0: mem 0xf4a01000-0xf4a010ff irq 16 at device 0.0 on pci2 sdhci_pci0: 1 slot(s) allocated pci2: at device 0.3 (no driver attached) pcib3: irq 17 at device 28.1 on pci0 pci3: on pcib3 iwn0: mem 0xf490-0xf4901fff irq 17 at device 0.0 on pci3 pcib4: irq 18 at device 28.2 on pci0 pci4: on pcib4 ehci1: mem 0xf5339000-0xf53393ff irq 23 at device 29.0 on pci0 usbus2: EHCI version 1.0 usbus2 on ehci1 isab0: at device 31.0 on pci0 isa0: on isab0 ahci0: port 0x6068-0x606f,0x6074-0x6077,0x6060-0x6067,0x6070-0x6073,0x6020-0x603f mem 0xf5338000-0xf53387ff irq 19 at device 31.2 on pci0 ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not
Re: FreeBSD 11 RC1 - no wifi
EDIT: It's a W 530, not a 540 On 08/23/2016 21:18, Stefan Wendler wrote: > Hi, > > I have upgraded from FreeBSD 10.3 to 11 RC1 on my Lenovo W450 with Intel > Centrino Ultimate-N 6300 > > After upgrade and a last reboot the iwn driver gets loaded but no iwn0 > interface pops up. Doing a 'service netif restart' crashes the machine > and a core is written. > > I have attached the output of the dmesg command. If somebody needs the > core, I can upload it somewhere and give you the download link. > > Please tell me how I can help you guys. > > Cheers, > Stefan > > > > ___ > 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" > -- Stefan Wendler stefan.wend...@tngtech.com +49 (0) 176 - 2438 3835 Senior Consultant TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterföhring Geschäftsführer: Henrik Klagges, Christoph Stock, Dr. Robert Dahlke Sitz: Unterföhring * Amtsgericht München * HRB 135082 ___ 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 11 RC1 - no wifi
Hi! > After upgrade and a last reboot the iwn driver gets loaded but no iwn0 > interface pops up. In 11, the hardware interfaces no longer appear. They still can be found with sysctl net.wlan.devices > Doing a 'service netif restart' crashes the machine > and a core is written. The crash should not happen. -- p...@opsec.eu+49 171 3101372 4 years to go ! ___ 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"
Subject: Re: NanoBSD install phase failing for releng/11
On Mon, Aug 22, 2016 at 01:08:11PM +0200, Guido Falsi wrote: Hi, While building a NanoBSD image using releng/11 sources I got this error message: ===> lib/libc++ (install) install -C -o root -g wheel -m 444 libc++.a /usr/local/nanobsd/rr-trunk/obj/_.w/usr/lib/ [...] /usr/local/nanobsd/rr-trunk/obj/_.w/usr/lib/libcxxrt.so install: symlink ../../lib/libcxxrt.so.1 -> /usr/local/nanobsd/rr-trunk/obj/_.w/usr/lib: File exists *** Error code 71 Stop. I'm seeing this error (symlink of libcxxrt.so.1 fails with diagnostic of prexisting file) in three seperate poudrieres, running on 12-current amd64s machines, while attempting to build or update 11-stable-amd64 jails. poudriere jail -j 11-stab-amd64 -u I've tried blowing the jail away and rebuilding; poudriere jail -d -j 11-stab-amd64 poudriere jail -c -j 11-stab-amd64 -m svn -v stable/11 but no luck; this fails as well, in the same way (and leaves me with no 11-stab-amd64 build jail, foo.) The 12-curr host machines are reasonably fresh builds - aubey2:/root # uname -a FreeBSD aubey2.bogons 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r304443: \ Thu Aug 18 23:46:18 MDT 2016 \ toor@aubey2.bogons:/usr/obj/usr/src/sys/GENERIC-NODEBUG amd64 chimera:/root # uname -a FreeBSD chimera.bogons 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r304224M: \ Tue Aug 16 11:08:38 MDT 2016 \ toor@chimera.bogons:/usr/obj/usr/src/sys/GENERIC-NODEBUG amd64 /etc/make.conf is NO_LPR=YES OPTIONS_SET=CUPS WITH_CUPS=YES CUPS_OVERWRITE_BASE=YES KERNCONF=GENERIC-NODEBUG MALLOC_PRODUCTION=yes SVN=/usr/bin/svnlite SVN_UPDATE=yes WITH_FAST_DEPEND=yes WITH_GALLIUM="YES" WITH_PKGNG=yes Some experimentation shows that "WITH_FAST_DEPEND=yes" isn't the issue; in or out, same result. log just before the fail is: ===> lib/libcxxrt (install) --- _libinstall --- install -N /usr/local/pd/jails/11-stab-amd64/usr/src/etc -C -o root -g wheel -m 444 libcxxrt.a /usr/local/pd/jails/11-stab-amd64/usr/lib/ install -N /usr/local/pd/jails/11-stab-amd64/usr/src/etc -C -o root -g wheel -m 444 libcxxrt_p.a /usr/local/pd/jails/11-stab-amd64/usr/lib/ install -N /usr/local/pd/jails/11-stab-amd64/usr/src/etc -s -o root -g wheel -m 444 libcxxrt.so.1 /usr/local/pd/jails/11-stab-amd64/lib/ install -N /usr/local/pd/jails/11-stab-amd64/usr/src/etc -o root -g wheel -m 444libcxxrt.so.1.debug /usr/local/pd/jails/11-stab-amd64/usr/lib/debug/lib/ install -N /usr/local/pd/jails/11-stab-amd64/usr/src/etc -l rs /usr/local/pd/jails/11-stab-amd64/lib/libcxxrt.so.1 /usr/local/pd/jails/11-stab-amd64/usr/lib/libcxxrt.so install: symlink ../../lib/libcxxrt.so.1 -> /usr/local/pd/jails/11-stab-amd64/usr/lib: File exists *** [_libinstall] Error code 71 make[5]: stopped in /usr/local/pd/jails/11-stab-amd64/usr/src/lib/libcxxrt 1 error make[5]: stopped in /usr/local/pd/jails/11-stab-amd64/usr/src/lib/libcxxrt *** [realinstall] Error code 2 make[4]: stopped in /usr/local/pd/jails/11-stab-amd64/usr/src/lib 1 error make[4]: stopped in /usr/local/pd/jails/11-stab-amd64/usr/src/lib *** [realinstall_subdir_lib] Error code 2 make[3]: stopped in /usr/local/pd/jails/11-stab-amd64/usr/src 1 error make[3]: stopped in /usr/local/pd/jails/11-stab-amd64/usr/src *** [reinstall] Error code 2 make[2]: stopped in /usr/local/pd/jails/11-stab-amd64/usr/src 1 error make[2]: stopped in /usr/local/pd/jails/11-stab-amd64/usr/src *** [installworld] Error code 2 make[1]: stopped in /usr/local/pd/jails/11-stab-amd64/usr/src 1 error make[1]: stopped in /usr/local/pd/jails/11-stab-amd64/usr/src *** [installworld] Error code 2 make: stopped in /usr/local/pd/jails/11-stab-amd64/usr/src 1 error make: stopped in /usr/local/pd/jails/11-stab-amd64/usr/src [00:35:57] >> Error: Failed to 'make installworld' 15113.866u 1497.004s 35:57.43 769.9%49262+602k 335984+2724910io 484194pf+0w regards, Ross -- Ross Alexander, (780) 675-6823 desk / (780) 689-0749 cell, r...@athabascau.ca "Plato's scheme of folly, which would have the philosophers take over the management of affairs, has been turned on its head; the men of affairs have taken over the direction and pursuit of knowledge." -- Thorstein Veblen, _The Higher Learning in America_ -- This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To uns
Re: FreeBSD 11 RC1 - no wifi
On 23.08.16 21:18, Stefan Wendler wrote: Hi, I have upgraded from FreeBSD 10.3 to 11 RC1 on my Lenovo W450 with Intel Centrino Ultimate-N 6300 After upgrade and a last reboot the iwn driver gets loaded but no iwn0 interface pops up. Doing a 'service netif restart' crashes the machine and a core is written. It's probably this bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211689#c4 I've attached a patch there that fixes this issue for me. -Jan ___ 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"
error writing to socket: Invalid argument with freebsd 11.0
___ 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"
termios cfmakeraw, disable buffer
Hi I'm having problem with the Wayland compositors. When opened the tty, it is set to raw mode with cfmakeraw and console is switched to graphics mode with ioctls. So far so good, however, when exiting the compositor (or I think when buffer is full) all the key presses that occurred in the Wayland compositor gets printed out in the console. How can I avoid this? Thanks! -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。 もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、 複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. ___ 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"
