from:"Beeblebrox"

My proposed plan did not work anyway, as both MINIMAL and GENERIC fail to build.
I'll have to clone the FreeBSD repo unless Shawn has something to comment on 
this.
___
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: snapshot of april 12th wont boot at all



Hello Ed.

> If this is reproducible on stock FreeBSD can you submit a PR with CPU details?
I don't have a cloned repo of FreeBSD, but AFAIK it's the "options PAX_*" 
related knobs in the kernel that, if eliminated, would revert the system to a 
FreeBSD one for all intents and purposes? I can just build MINIMAL or GENERIC 
and try if that's the case.

Separate finding I have for this CPU is that with an unlocked 4th core (gets 
detected as Phenom II X4 B60 instead of Athlon II X3) observable oddities are:
* Some ports have runaway builds under poudriere, end up filling swap and fail. 
www/webkit-gtk2 is an example. This could also be due to separate src.conf 
settings used to build the poudriere jail world.
* Xorg desktop becomes jittery, mouse control is difficult.
Mentioning these to ask whether you prefer them to be included in PR?

Regards.
___
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: snapshot of april 12th wont boot at all

Hey Shawn,

> What happens when you set vm.pmap.pti=0 at the loader prompt?
Yep, that fixed it. Booted into MYKERN without problem.
Assuming Page Table Isolation still a bit buggy?

FreeBSD 12.0-CURRENT #3 5b8586c22aa(hardened/current/master):
Tue Apr 17 08:11:53 EDT 2018

Regards.

-- 
HardenedBSD_amd64_12-Current_RadeonKMS
Please CC my email when responding, mail from list is not delivered.
___
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"

snapshot of april 12th wont boot at all

I have (possibly) similar problem, running kernel from March 29 as
fall-back (older kernel, latest world).

* OS: HardenedBSD-12 on amd64 Athlon II X3 460
* Kernels built yesterday: MYKERN & HARDENEDBSD (GENERIC with Debug).
  Both kernels fail. No errors encountered during buildworld/kernel.
  World installs normally.
* Boot process: Grub -> /boot/loader -> Kernel Selection. No EFI (MBR).
  Grub has own partition (ext2fs), /boot/loader on ZFS.
* zpool: Striped on 2 HDD's, scrub returns clean pool.

FAILURE POINT: System freeze, completely unresponsive, requires hard
reset.
* Initially seems like failure is at "Mount Root from zpool/ROOT/bsd".
  Further inspection of dmesg shows garbled text at services stage
  (start reading /etc/rc.conf)
* /etc/rc.conf: Everything disabled for bug hunting. Cause does not
  seem related to linux / radeonkms either.
* Selecting "Safe Mode" (kern.smp.disabled ?) gets me to single-user
  mode, and later multi-user but system freezes as soon as I login.
  Not 100% sure about this behaviour though, as I have been at it since
  early morning yesterday.
* Have not tried with ACPI disabled. Dmesg: Firmware Warning (ACPI):
  32/64X length mismatch in FADT/Gpe0Block: 64/32 (20180313/tbfadt-748)

There was a recent bug involving databases failing to start due to
"limits: NO: No such file or directory". I have Mariadb-Server-100
installed with the new patch for this bug. I wonder whether these two
could be related?

Would prefer not posting my verbose boot log dmesg file here, can email
it (or download link) to developers (at FreeBSD.org) if needed though.

Regards.

-- 
HardenedBSD_amd64_12-Current_RadeonKMS
Please CC my email when responding, mail from list is not delivered.
___
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: Call for Testing: UEFI Changes

2018-04-05 Thread Zaphod Beeblebrox

As I said I would, I put the contents of /boot onto the FAT-formated EFI
partition.  This is suboptimal.  The default is to use "kernel.old" ...
etc  ... which cannot be done on a FAT partition... at least not with our
filesystem driver ...

... but with all of /boot on the EFI partition, simply starting loader.efi
works.

On Wed, Apr 4, 2018 at 11:57 AM, Kyle Evans  wrote:

> On Wed, Mar 21, 2018 at 7:45 PM, Kyle Evans  wrote:
> > Hello!
> >
> > A number of changes have gone in recently pertaining to UEFI booting
> > and UEFI runtime services. The changes with the most damaging
> > potential are:
> >
> > We now put UEFI runtime services into virtual address mode, fixing
> > runtime services with U-Boot/UEFI as well as the firmware
> > implementation in many Lenovos. The previously observed behavior was a
> > kernel panic upon invocation of efibootmgr/efivar, or a kernel panic
> > just loading efirt.ko or compiling EFIRT into the kernel.
> >
> > Graphics mode selection is now done differently to avoid regression
> > caused by r327058 while still achieving the same effect. The observed
> > regression was that the kernel would usually end up drawing
> > incorrectly at the old resolution on a subset of the screen, due to
> > incorrect framebuffer information.
> >
> > Explicit testing of these changes, the latest of which happened in
> > r331326, and any feedback from this testing would be greatly
> > appreciated. Testing should be done with either `options EFIRT` in
> > your kernel config or efirt.ko loaded along with updated bootloader
> > bits.
> >
> > I otherwise plan to MFC commits involved with the above-mentioned
> > changes by sometime in the first week of April, likely no earlier than
> > two (2) weeks from now on April 4th.
> >
> > Thanks,
> >
> > Kyle Evans
>
> As partially promised, the non-graphics related changes have been
> MFC'd to stable/11 today as r332028.
>
> The graphics related changes are going to simmer longer and probably
> get ripped out, because we're bad at this.
>
> Thanks,
>
> Kyle Evans
> ___
> 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: Call for Testing: UEFI Changes

2018-04-03 Thread Zaphod Beeblebrox

If you're thinking on it,  you should know that the DVD version works.  The
difference, AFAICT, is that it simply calls loader.efi directly.  Ie:
bootx64.efi is loader.efi, not boot1.efi.

Loader.efi doesn't seem to change the screen mode when it starts.  When the
kernel starts afterwards, this all just works.

I assume loader.efi works here because CD9660 is a format supported by
EFI.  Thus loader.efi can directly read it.  That and/or loader can work
with the device is was started from.

When I start boot1.efi on this system, it changes mode, then it continues.

... so if you've got a boot1.efi that doesn't change mode, can you post
that binary for me to try ... ?

On Tue, Apr 3, 2018 at 4:48 PM, Kyle Evans  wrote:

> On Tue, Apr 3, 2018 at 3:17 PM, Kyle Evans  wrote:
> > Hi,
> >
> > Right- so, `gop set 0` should've immediately cleared your screen and
> > put it into 1920x1080, full stop. If it did not, I think that's
> > indicative of some kind of interestingly broken firmware...
> >
> > Regardless! We're clearly bad at trying to set a mode before the
> > kernel starts, so r331904 sets the default max resolution in such a
> > way that we just don't change the resolution by default anymore and
> > interested parties can bump that up if they want to try it. This
> > Thursday's snapshots should have this included.
>
> After reviewing the video again and discussing it with manu, I don't
> think that commit's going to solve your problem at all... we'll need
> to re-think this one a bit more.
>
> > I think if we're going to change modes as a default, we should have
> > some way for vt/efifb to use EFIRT or be notified by EFIRT of
> > supported resolutions so that vt/efifb can hopefully just handle it
> > all and do it properly. This approach would be more similar I guess to
> > how KMS drivers operate, and less fragile than what we're seeing with
> > these different approaches we've taken.
> >
>
___
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: Call for Testing: UEFI Changes

2018-04-03 Thread Zaphod Beeblebrox

I did as you asked.  You can see the result at:
https://owncloud.towernet.ca/s/6K3pGknCyGTi7du

... but the long and short of it is that even though the loader is printing
in the center of the screen (text mode?), it sees the 1920x1080 mode as the
"mode 0" ... I even tried "gop set 0" ... which it accepted, but then
continuing to boot produced what you see in the video.

I think, since it's in the cetner of the screen, that we're looking at
80x25 text... which is ... 800 x 600 -ish?  The kernel definately wants
graphics again ... but ... I dunno ... is it getting it?  Is the 80x25 text
mode emulated on a bitmapped screen?


On Mon, Apr 2, 2018 at 9:07 PM, Kyle Evans <kev...@freebsd.org> wrote:

> On Mon, Apr 2, 2018 at 5:51 PM, Zaphod Beeblebrox <zbee...@gmail.com>
> wrote:
> > On Sun, Apr 1, 2018 at 7:41 PM, David NewHamlet <wheelcomp...@gmail.com>
> > wrote:
> >>
> >> Fixed in: FreeBSD-12.0-CURRENT-amd64-20180329-r331740-disc1.iso
> >>
> >>
> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176694
> >>
> >> On Mon, Apr 2, 2018 at 12:38 AM, Tomoaki AOKI <
> junch...@dec.sakura.ne.jp>
> >> wrote:
> >>
> >> > Confirmed both loader (with boot1) part and efirt.ko part.
> >> > Working OK on my ThinkPad420 (with nvidia GPU) at r331864.
> >> >
> >> > No benefit (VGA resolution) but no new harm (no panic nor silent
> >> > reboot).
> >> >
> >> >  *Maybe gracefully falling back to mode 0.
> >> >
> >> > As I'm on x11/nvidia-driver, completely no test is done with
> >> > drm-next.
> >> >
> >> > One more to mention.
> >> > I've cherry-picked r330868, r331241 and r331361 on stable/11 after
> >> > r331114, amd64 and works OK as on head.
> >> > Additional cherry-picking of r331365 is OK, too.
> >> >
> >> > Without r330868, my ThinkPad silently reboots within about 10-60
> >> > minutes range, maybe by actual access to UEFI RS.
> >> > With r331241 without r331361 causes instant panic on loading efirt.ko.
> >> > So all 3 (4) revs should be MFC'ed together.
> >> >
> >> > Sorry for delay.
> >> >
> >> >
> >> > On Thu, 22 Mar 2018 10:34:33 -0500
> >> > Kyle Evans <kev...@freebsd.org> wrote:
> >> >
> >> > > On Thu, Mar 22, 2018 at 10:18 AM, Kyle Evans <kev...@freebsd.org>
> >> > > wrote:
> >> > > > On Thu, Mar 22, 2018 at 10:16 AM, Peter Lei <peter@ieee.org>
> >> > wrote:
> >> > > >> On 3/22/18 8:56 AM, Tomoaki AOKI wrote:
> >> > > >>> Hi.
> >> > > >>> For problem 2, try reverting r331241 alone.
> >> > > >>> This worked for my ThinkPad T420.
> >> > > >>
> >> > > >>
> >> > > >> I also hit this after updating to latest and was about to post
> when
> >> > > >> I
> >> > > >> saw this thread -
> >> > > >>
> >> > > >> I build efirt into the kernel and it's now doing a panic on boot.
> >> > > >> It
> >> > > >> appears to be due to this recent addition in dev/efidev/efirt.c
> by
> >> > r331241:
> >> > > >>
> >> > > >>> if (!efi_is_in_map(map, efihdr->memory_size /
> >> > efihdr->descriptor_size,
> >> > > >>> efihdr->descriptor_size,
> >> > > >>> (vm_offset_t)efi_runtime->rt_gettime))
> >> > {
> >> > > >>
> >> > > >> The faulting address is for "efi_runtime->rt_gettime" (and is
> still
> >> > > >> a
> >> > > >> phys addr here).
> >> > > >>
> >> > > >
> >> > > > The following patch [1] (I can't guarantee how long he'll keep it
> >> > > > available there) should fix this class of problems.
> >> > > >
> >> > > > [1] https://people.freebsd.org/~andrew/0001-Enter-into-the-
> >> > EFI-environment-before-check-the-GetT.patch
> >> > >
> >> > > Now committed as of r331361.
> >> > > ___
> >> > > freebsd-current@freebsd.org mailing list
> >> > > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> >> &g

Re: Call for Testing: UEFI Changes

2018-04-02 Thread Zaphod Beeblebrox

I've booted that image on my zbook 15.  I show in the boot that I can
deliberately load efirt.ko ... and it doesn't help.  I also show that I can
"type blind" after the system boots ... so everything but the screen is
working.

In case you can't quite make it out, I hit right cursor twice (move to the
"live cd" choice) and hit enter.  Then I type "root" enter and then
"reboot" ...

https://youtu.be/tlmaVJ-3aq0

(The rock sound track is just free audio to mask a barking dog and a radio
in the background.)


On Sun, Apr 1, 2018 at 7:41 PM, David NewHamlet 
wrote:

> Fixed in: FreeBSD-12.0-CURRENT-amd64-20180329-r331740-disc1.iso
>
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176694
>
> On Mon, Apr 2, 2018 at 12:38 AM, Tomoaki AOKI 
> wrote:
>
> > Confirmed both loader (with boot1) part and efirt.ko part.
> > Working OK on my ThinkPad420 (with nvidia GPU) at r331864.
> >
> > No benefit (VGA resolution) but no new harm (no panic nor silent
> > reboot).
> >
> >  *Maybe gracefully falling back to mode 0.
> >
> > As I'm on x11/nvidia-driver, completely no test is done with
> > drm-next.
> >
> > One more to mention.
> > I've cherry-picked r330868, r331241 and r331361 on stable/11 after
> > r331114, amd64 and works OK as on head.
> > Additional cherry-picking of r331365 is OK, too.
> >
> > Without r330868, my ThinkPad silently reboots within about 10-60
> > minutes range, maybe by actual access to UEFI RS.
> > With r331241 without r331361 causes instant panic on loading efirt.ko.
> > So all 3 (4) revs should be MFC'ed together.
> >
> > Sorry for delay.
> >
> >
> > On Thu, 22 Mar 2018 10:34:33 -0500
> > Kyle Evans  wrote:
> >
> > > On Thu, Mar 22, 2018 at 10:18 AM, Kyle Evans 
> wrote:
> > > > On Thu, Mar 22, 2018 at 10:16 AM, Peter Lei 
> > wrote:
> > > >> On 3/22/18 8:56 AM, Tomoaki AOKI wrote:
> > > >>> Hi.
> > > >>> For problem 2, try reverting r331241 alone.
> > > >>> This worked for my ThinkPad T420.
> > > >>
> > > >>
> > > >> I also hit this after updating to latest and was about to post when
> I
> > > >> saw this thread -
> > > >>
> > > >> I build efirt into the kernel and it's now doing a panic on boot. It
> > > >> appears to be due to this recent addition in dev/efidev/efirt.c by
> > r331241:
> > > >>
> > > >>> if (!efi_is_in_map(map, efihdr->memory_size /
> > efihdr->descriptor_size,
> > > >>> efihdr->descriptor_size, (vm_offset_t)efi_runtime->rt_
> gettime))
> > {
> > > >>
> > > >> The faulting address is for "efi_runtime->rt_gettime" (and is still
> a
> > > >> phys addr here).
> > > >>
> > > >
> > > > The following patch [1] (I can't guarantee how long he'll keep it
> > > > available there) should fix this class of problems.
> > > >
> > > > [1] https://people.freebsd.org/~andrew/0001-Enter-into-the-
> > EFI-environment-before-check-the-GetT.patch
> > >
> > > Now committed as of r331361.
> > > ___
> > > freebsd-current@freebsd.org mailing list
> > > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@
> > freebsd.org"
> > >
> >
> >
> > --
> > Tomoaki AOKI
> > ___
> > freebsd-current@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-unsubscribe@
> 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"
>
___
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"

buildworld ABSOLUTE_PATH

2018-03-17 Thread Beeblebrox

I'm building multiple worlds with different src.conf settings.
Would it be too much of a PIA to to introduce
ABSOLUTE_PATH to override MAKEOBJDIRPREFIX ?

This would facilitate 2 problems:
1. Default practice of appending SRC_PATH to PREFIX causes a ridiculous 
folder structure
2. The folder ending can be customised such as amd64.host, amd64.jails

Handling the rest via shell script would become an easier task IMHO if
this could be implemented.

Regards.

-- 
Please CC my email when responding, mail from list is not delivered.
___
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: Intel CPU design flaw - FreeBSD affected?

2018-01-02 Thread Zaphod Beeblebrox

>From the information that was leaked by AMD claiming that their processors
didn't have the flaws, it would seem any OS in which the kernel occupies
the same address space as the userland would be vulnerable.  The AMD post
implied that Intel's speculative execution of code did not check the
validity of the operands before speculatively executing the code.  I
suppose the implication is that the security check "catches up" with the
speculative execution at some point ... and that their (AMD's) microcode
did check.

Anyways... for those keeping score at home, this is a privilege escalation
bug... so it's only really useful in concert with other bugs ... but still
pretty huge.

Some estimate that between 5% and 30% performance degradation may be
unavoidable.  Some say it's worse or can't be fully fixed.

Certainly, the sunk cost of current CPUs is a huge issue for server farm
vendors like Amazon and/or google.

On Tue, Jan 2, 2018 at 6:13 PM, Michael Butler 
wrote:

> Has any impact assessment been made as to FreeBSD's exposure or
> mitigation strategies?
>
> 'Kernel memory leaking' Intel processor design flaw forces Linux,
> Windows redesign - The Register
>
> https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/
>
>
___
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"

src.conf clang x-build flags

2017-05-26 Thread Beeblebrox

Is there any hope we will get src.conf flags to specify which clang x-build
tools world builds? For example build for i386 but not ARM.?
___
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: Anyone having ccache errors?

> Would you please execute the following and attach your output?
> $ make -VMAKE_VERSION

make ver: 20170510
uname -U: 1200030

In my original post I also stated:
also getting "cc not found" errors whether ccache is enabled or not.
For example installworld (no ccache) broke with that message so I
decided to re-build.

So there's some strange clang stuff going on...

-- 
FreeBSD_amd64_12-Current_RadeonKMS
Please CC my email when responding, mail from list is not delivered.
___
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: Anyone having ccache errors?

> I was looking at the "make: Unknown modifier ‘c’” warnings — which
> were a symptom of the bug that was fixed late last week. I don’t
> genuinely know if ccache works or doesn’t work. Thanks, -Ngie

Thanks,
I still do see those exact "make: Unknown modifier ‘c’” warnings
along with the original fail.

-- 
FreeBSD_amd64_12-Current_RadeonKMS
Please CC my email when responding, mail from list is not delivered.
___
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: Anyone having ccache errors?

> Upgrade make — it was a bug with it, fixed in the past few days.
> HTH,

I just rebuilt and installed a clean world without using ccache
After reboot I tried buildworld with ccache enabled, but got same error.

So, did not work unless you meant a particular port?

-- 
FreeBSD_amd64_12-Current_RadeonKMS
Please CC my email when responding, mail from list is not delivered.
___
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"

Anyone having ccache errors?

I have been getting ccache errors during buildworld. Ports for example does not 
have this problem. I compleely reset the cache data some 2 months ago and 
ccache seemed to play with that much more nicely.

Apart from the error below, I'm also getting some "cc not found" errors when 
doing src stuff, whether ccache is enabled or not. For example installworld (no 
ccache) broke with that message so I decided to re-build.

uname: 12.0-CURRENT 1200028 bedc15ffb71(drm-next)-dirty: Thu Apr 20 2017

/etc/make.conf
CC:=${CC:C,^cc,/usr/local/libexec/ccache/world/clang,1}
CXX:=${cxx:c,^C\+\+,/usr/local/libexec/ccache/world/clang++,1}

ls /usr/local/libexec/ccache/world/
c++   CCclang clang++40 g++5
ccccacheclang++   clang40   gcc5

# make buildworld =>
make: Unknown modifier 'c'
make: Unknown modifier 'c'
make[1]: Unknown modifier 'c'
make[1]: Unknown modifier 'c'
make[2]: Unknown modifier 'c'
make[2]: Unknown modifier 'c'
make[2]: Unknown modifier 'c'
make[2]: Unknown modifier 'c'
--
>>> World build started
.
>>> stage 1.2: bootstrap tools
--
cd /asp/git/src; MAKEOBJDIRPREFIX=/asp/obj/asp/git/src/tmp  INSTALL="sh 
/asp/git/src/tools/install.sh"  TOOLS_PREFIX=/asp/obj/asp/git/src/tmp  
PATH=/asp/obj/asp/git/src/tmp/legacy/usr/sbin:/asp/obj/asp/git/src/tmp/legacy/usr/bin:/asp/obj/asp/git/src/tmp/legacy/bin:/sbin:/bin:/usr/sbin:/usr/bin
  WORLDTMP=/asp/obj/asp/git/src/tmp  MAKEFLAGS="-m /asp/git/src/tools/build/mk  
-m /asp/git/src/share/mk" make  -f Makefile.inc1  DESTDIR=  
BOOTSTRAPPING=1200030  SSP_CFLAGS=  MK_HTML=no NO_LINT=yes MK_MAN=no  -DNO_PIC 
MK_PROFILE=no -DNO_SHARED  -DNO_CPU_CFLAGS MK_WARNS=no MK_CTF=no  
MK_CLANG_EXTRAS=no MK_CLANG_FULL=no  MK_LLDB=no MK_TESTS=no  MK_INCLUDES=yes 
bootstrap-tools
make[2]: Unknown modifier 'c'
make[2]: Unknown modifier 'c'
===> lib/clang/libllvmminimal (obj,all,install)
make[3]: Unknown modifier 'c'
make[3]: Unknown modifier 'c'
make[3]: Unknown modifier 'c'
make[3]: Unknown modifier 'c'
make[3]: Unknown modifier 'c'
-O2 -pipe -I/asp/git/src/lib/clang/include -I/asp/git/src/contrib/llvm/include 
-DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS 
-DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd12.0\" 
-DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd12.0\" 
-DDEFAULT_SYSROOT=\"/asp/obj/asp/git/src/tmp\" -ffunction-sections 
-fdata-sections -DNDEBUG -MD -MF.depend.Support_APInt.o -MTSupport/APInt.o 
-Qunused-arguments -I/asp/obj/asp/git/src/tmp/legacy/usr/include -std=c++11 
-fno-exceptions -fno-rtti  -stdlib=libc++ -Wno-c++11-extensions  -c 
/asp/git/src/contrib/llvm/lib/Support/APInt.cpp -o Support/APInt.o
/bin/sh: -O2: not found
*** Error code 127

Stop.
make[3]: stopped in /asp/git/src/lib/clang/libllvmminimal



* I had asked this before, but got no answer. I assume it's not possible then?
> 1. For buildworld, my /etc/src.conf uses default CROSS_COMPILER,
> CLANG_BOOTSTRAP, CLANG_FULL  for amd64, but I would like clang to
> xbuild only for target i386 as I do not need the others (like
> Target/arm). Is there a knob for this?

-- 
FreeBSD_amd64_12-Current_RadeonKMS
Please CC my email when responding, mail from list is not delivered.
___
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: Several minor questions (12.0-amd64)

2017-04-24 Thread Beeblebrox

/boot/loader.conf allows for an earlier time frame
for having dumpdev.


Thanks a lot, that's a very nice suggestion.
Did not work though surprisingly, which suggests panic is ocuring in a way
that interferes with loader. No matter, I noted down the output of trace
and had alredy moved relevant modules to rc.conf. The capture attempt was
so I could send it to a drm-next developer.

Regards.
___
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"

Several minor questions (12.0-amd64)

2017-04-22 Thread Beeblebrox

Hello, I have several brief questions on issues I'm slightly stuck on:

1. For buildworld, my /etc/src.conf uses default CROSS_COMPILER,
CLANG_BOOTSTRAP, CLANG_FULL  for amd64, but I would like clang to xbuild
only for target i386 as I do not need the others (like Target/arm). Is
there a knob for this?

2. Is there a way to read a list of modules inside an unloaded kernel? Sort
of "kldstat -v" for a non-loaded kernel? Reading the kernel manifest
(INCLUDE_CONFIG_FILE setting) is not what I need.

3. Under one scenario, I'm getting a kernel panic but I cannot dump because
busybox states "no dumpdev specified" which means rc.conf (where I have
dumpdev set) has not been read yet. How can I pass dumpdev wile in busybox
command line so that ">dump" does its job?

4. Getting several of these lock order reversals. Kernel is drm-next but
Generic from Head gives the same messages. Not urgent, just FYI.

lock order reversal:
 1st 0xf80064915040 filedesc structure (filedesc structure) @
/asp/git/srcdrm/sys/kern/kern_descrip.c:1234
 2nd 0xf8002e9f0d50 ufs (ufs) @
/asp/git/srcdrm/sys/kern/vfs_subr.c:5022
 stack backtrace:
 #0 0x804d3180 at witness_debugger+0x70
 #1 0x804d3073 at witness_checkorder+0xe23
 #2 0x8044aa35 at __lockmgr_args+0x875
 #3 0x814d09e5 at ffs_lock+0xa5
 #4 0x80717840 at VOP_LOCK1_APV+0xe0
 #5 0x8054847a at _vn_lock+0x6a
 #6 0x8042c9c8 at knlist_remove_kq+0x88
 #7 0x8053f358 at filt_vfsdetach+0x28
 #8 0x8042d4f1 at knote_fdclose+0x171
 #9 0x804206b5 at closefp+0x65
 #10 0x806afe9a at amd64_syscall+0x57a
 #11 0x80692dcb at Xfast_syscall+0xfb

 lock order reversal:
 1st 0xf80064915040 filedesc structure (filedesc structure) @
/asp/git/srcdrm/sys/kern/kern_descrip.c:1234
 2nd 0xf8004b4d3d50 zfs (zfs) @
/asp/git/srcdrm/sys/kern/vfs_subr.c:5022
 stack backtrace:
 #0 0x804d3180 at witness_debugger+0x70
 #1 0x804d3073 at witness_checkorder+0xe23
 #2 0x8044a0fe at lockmgr_lock_fast_path+0x1ce
 #3 0x80717840 at VOP_LOCK1_APV+0xe0
 #4 0x8054847a at _vn_lock+0x6a
 #5 0x8042c9c8 at knlist_remove_kq+0x88
 #6 0x8053f358 at filt_vfsdetach+0x28
 #7 0x8042d4f1 at knote_fdclose+0x171
 #8 0x804206b5 at closefp+0x65
 #9 0x806afe9a at amd64_syscall+0x57a
 #10 0x80692dcb at Xfast_syscall+0xfb

 lock order reversal:
 1st 0xf801aec715f0 syncer (syncer) @
/asp/git/srcdrm/sys/kern/vfs_subr.c:2152
 2nd 0xf8004bc3e068 zfs (zfs) @
/asp/git/srcdrm/sys/kern/vfs_subr.c:2602
 stack backtrace:
 #0 0x804d3180 at witness_debugger+0x70
 #1 0x804d3073 at witness_checkorder+0xe23
 #2 0x8044a0fe at lockmgr_lock_fast_path+0x1ce
 #3 0x80717840 at VOP_LOCK1_APV+0xe0
 #4 0x8054847a at _vn_lock+0x6a
 #5 0x80538892 at vget+0x82
 #6 0x8053a936 at vfs_msync+0xa6
 #7 0x8053ef96 at sync_fsync+0xc6
 #8 0x80716890 at VOP_FSYNC_APV+0xe0
 #9 0x8053d2fc at sched_sync+0x36c
 #10 0x80436f44 at fork_exit+0x84
 #11 0x8069301e at fork_trampoline+0xe

 lock order reversal:
 1st 0xf80039590d50 zfs (zfs) @
/asp/git/srcdrm/sys/kern/vfs_mount.c:855
 2nd 0xf8001a4489a0 devfs (devfs) @
/asp/git/srcdrm/sys/kern/vfs_subr.c:2602
 stack backtrace:
 #0 0x804d3180 at witness_debugger+0x70
 #1 0x804d3073 at witness_checkorder+0xe23
 #2 0x8044a0fe at lo
 ckmgr_lock_fast_path+0x1ce
 #3 0x80717840 at VOP_LOCK1_APV+0xe0
 #4 0x8054847a at _vn_lock+0x6a
 #5 0x80538892 at vget+0x82
 #6 0x80395b2d at devfs_allocv+0xcd
 #7 0x80395643 at devfs_root+0x43
 #8 0x8052f66f at vfs_donmount+0x118f
 #9 0x8052e4b2 at sys_nmount+0x72
 #10 0x806afe9a at amd64_syscall+0x57a
 #11 0x80692dcb at Xfast_syscall+0xfb
___
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: Trying to read linux-lvm on 11.0-RC2 using geom, bhyve, fail.

2016-09-18 Thread Zaphod Beeblebrox

On Fri, Sep 16, 2016 at 1:06 AM, Allan Jude <allanj...@freebsd.org> wrote:

> On 2016-09-16 01:04, Zaphod Beeblebrox wrote:
> >
> >
> >
> > Are you using zvols to back the VMs? Make sure they are in
> 'volmode=dev'
> > not 'geom' (the default), or GEOM will lock the device when it
> detects a
> > partition table being written to the zvol (from the installer inside
> > the VM)
> >
> > Note that this setting requires you to export/import the pool or
> reboot
> > to apply.
> >
> >
> > No, no.  The whole point here is that I was booting the raw disk.
> > "ada1" as it were.
> >
>
> You might try the dangerous 'shoot yourself in the foot mode' for geom:
>
> man 4 geom:
> 0x10 (allow foot shooting)
> Allow writing to Rank 1 providers.  This would, for example,
> allow the super-user to overwrite the MBR on the root disk or
> write random sectors elsewhere to a mounted disk.  The
> implications are obvious.
>
>
> sysctl kern.geom.debugflags=16
>
> I get where you're going here, but it doesn't apply because at this point
> I'm not even booting from ada1.
>
___
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: Trying to read linux-lvm on 11.0-RC2 using geom, bhyve, fail.

2016-09-15 Thread Zaphod Beeblebrox

> Are you using zvols to back the VMs? Make sure they are in 'volmode=dev'
> not 'geom' (the default), or GEOM will lock the device when it detects a
> partition table being written to the zvol (from the installer inside the
> VM)
>
> Note that this setting requires you to export/import the pool or reboot
> to apply.
>

No, no.  The whole point here is that I was booting the raw disk.  "ada1"
as it were.
___
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"

Trying to read linux-lvm on 11.0-RC2 using geom, bhyve, fail.

2016-09-14 Thread Zaphod Beeblebrox

I'm converting some Xen/Debian/Windows domain servers to
FreeBSD/Bhyve/Samba domain servers. Windows is still required for a couple
of applications, but I've recently had enough success with Samba4 to try
this.  Not the problem.

The machines have two disks (was RAID-1 before, will be RAID-1 after) and
I've run the FreeBSD install on one disk leaving the other alone.  I'd like
to copy off some of what's on the other disk, so I set about trying to read
it.

BHYVE ATTEMPT

Believe-it-or-not, I tried bhyve first.  Being the more complex solution,
of course.  I tried booting the other disk in bhyve.  I chalked that
failure up to it still being a Xen config... wasn't sure how that would
boot for fail under bhyve... so I grabbed a debian live CD from the net and
tried to boot it.

Now, I'm following the directions from
https://www.freebsd.org/doc/handbook/virtualization-host-bhyve.html ...

And the error both times was failing to find init.  Both booting the CD
_and_ booting the disk.

I can't seem to find any further documentation on my problem.  Linux boots
to it's initrd filesystem state and fails to leave it because it (claims
it) can't find /sbin/init (even though in the CD case, it's there)

GEOM ATTEMPT

After this fail, I decided I didn't really _need_ to run linux here and I
discovered 'geom_linux_lvm.ko' ... cool.  But fail, too.  Doesn't emit any
messages.  I even enabled the debug messages for it.

The linux disk is partitioned thusly:

=>63  1953525105  ada1  MBR  (932G)
  631985- free -  (993K)
2048  1953523120 1  linux-data  [active]  (932G)
___
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: Unstable kernel (dumbbell) crashes

2015-12-20 Thread Beeblebrox

I forgot version data, sorry.

 11.0-CURRENT #0 831e725(master): Wed Dec 16
___
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"

Unstable kernel (dumbbell) crashes

2015-12-20 Thread Beeblebrox

Hello.

I have been away from my FreeBSD system for over 7 months. The first on my 
return was to update world/kernel then do a full poudriere run for all my 
packages. The process had many problems; I'm reporting items below as FYI.
I'm tracking https://github.com/dumbbell/freebsd.git for my Radeon card.

1. installworld ran into same problem as below and I got around it by following 
the prescription therein: 
https://lists.freebsd.org/pipermail/freebsd-testing/2015-September/001094.html
Reviewing the questions asked in the thread, I find nothing of significance in 
my particular case. Thus, still a mystery.

2. The pkgng DB has become buggy & inconsistent. I am preparing to "pkg delete 
-a" and re-install all from a list after the poudriere run finishes.

3. The newly built kernel keeps crashing and re-booting unpredictably. The 
poudriere run seems to have something to do with triggering this.

4. Service dbus still fails to start from /etc/rc.conf (which prevents xorg 
login) and must be started manually.

5. I built and booted into a DEBUG kernel. The system quickly becomes unstable 
and eventually the simplest commands (ls or cat) take over 60 secs to respond. 
File containing dmesg output and memory status is attached. However, Memory 
status seems to be a symptom and not a cause. 

Regards.

-- 
FreeBSD_amd64_11-Current_RadeonKMS
Please CC my email when responding, mail from list is not delivered.
Expensive timeout(9) function: 0x808b5480(0x8180a708) 
0.021493024 s
Expensive timeout(9) function: 0x80c98620(0) 3.963288769 s
lock order reversal:
 1st 0xf8002d4dc068 zfs (zfs) @ /asp/git/src/sys/kern/vfs_mount.c:1224
 2nd 0xf8002d4db7b8 zfs_gfs (zfs_gfs) @ 
/asp/git/src/sys/cddl/contrib/opensolaris/uts/common/fs/gfs.c:494
stack backtrace:
#0 0x80a77150 at witness_debugger+0x70
#1 0x80a77051 at witness_checkorder+0xe71
#2 0x809f8607 at __lockmgr_args+0xd47
#3 0x80abf06c at vop_stdlock+0x3c
#4 0x80f76cb0 at VOP_LOCK1_APV+0x100
#5 0x80ae1082 at _vn_lock+0xc2
#6 0x82069b23 at gfs_file_create+0x73
#7 0x82069bcd at gfs_dir_create+0x1d
#8 0x821309e7 at zfsctl_mknode_snapdir+0x47
#9 0x8206a145 at gfs_dir_lookup+0x185
#10 0x8206a62d at gfs_vop_lookup+0x1d
#11 0x8212fa05 at zfsctl_root_lookup+0xf5
#12 0x821308a3 at zfsctl_umount_snapshots+0x83
#13 0x8214958b at zfs_umount+0x7b
#14 0x80ac8c10 at dounmount+0x530
#15 0x80ac864d at sys_unmount+0x35d
#16 0x80e2b519 at amd64_syscall+0x2f9
#17 0x80e0acdb at Xfast_syscall+0xfb
lock order reversal:
 1st 0xf8002d5978e0 filedesc structure (filedesc structure) @ 
/asp/git/src/sys/kern/kern_descrip.c:1231
 2nd 0xf8014526f7b8 zfs (zfs) @ /asp/git/src/sys/kern/vfs_subr.c:4752
stack backtrace:
#0 0x80a77150 at witness_debugger+0x70
#1 0x80a77051 at witness_checkorder+0xe71
#2 0x809f8607 at __lockmgr_args+0xd47
#3 0x80abf06c at vop_stdlock+0x3c
#4 0x80f76cb0 at VOP_LOCK1_APV+0x100
#5 0x80ae1082 at _vn_lock+0xc2
#6 0x809daffe at knlist_remove_kq+0x7e
#7 0x80ad7c58 at filt_vfsdetach+0x28
#8 0x809db8d7 at knote_fdclose+0xc7
#9 0x809cfb85 at closefp+0x65
#10 0x80e2b519 at amd64_syscall+0x2f9
#11 0x80e0acdb at Xfast_syscall+0xfb
pid 37436 (gvfsd), uid 1001: exited on signal 5
lock order reversal:
 1st 0xf8001b0f42d8 syncer (syncer) @ /asp/git/src/sys/kern/vfs_subr.c:1983
 2nd 0xf80145b7d068 zfs (zfs) @ /asp/git/src/sys/kern/vfs_subr.c:2435
stack backtrace:
#0 0x80a77150 at witness_debugger+0x70
#1 0x80a77051 at witness_checkorder+0xe71
#2 0x809f8607 at __lockmgr_args+0xd47
#3 0x80abf06c at vop_stdlock+0x3c
#4 0x80f76cb0 at VOP_LOCK1_APV+0x100
#5 0x80ae1082 at _vn_lock+0xc2
#6 0x80ad07d6 at vget+0x146
#7 0x80ad2c96 at vfs_msync+0x66
#8 0x80ad7916 at sync_fsync+0xc6
#9 0x80f759c5 at VOP_FSYNC_APV+0x115
#10 0x80ad5c74 at sched_sync+0x3e4
#11 0x809e45c4 at fork_exit+0x84
#12 0x80e0af2e at fork_trampoline+0xe



SYSTEM MEMORY INFORMATION:
mem_wire:5383413760 (   5134MB) [ 66%] Wired: disabled for paging out
mem_active:  + 90443776 ( 86MB) [  1%] Active: recently referenced
mem_inactive:+   2483912704 (   2368MB) [ 30%] Inactive: recently not referenced
mem_cache:   +0 (  0MB) [  0%] Cached: almost avail. for 
allocation
mem_free:+ 92983296 ( 88MB) [  1%] Free: fully available for 
allocation
mem_gap_vm:  +16384 (  0MB) [  0%] Memory gap: UNKNOWN
--  --- --
mem_all: =   8050769920 (   7677MB) [100%] Total real memory managed
mem_gap_sys: +232927232 (222MB)Memory gap: Kernel?!
--  ---
mem_phys:=   8283697152 (   7899MB)Total real memory available

Re: system failure: cannot kill webkit-gtk3 if using dumbell/radeon

2015-03-04 Thread Beeblebrox

Hi.
Sorry for the delay to get back to you (including your private emails).
Not a problem, those were various reports left to your judgment as to their
significance. Better to provide more information rather than less.

slim failure: Traced to dbus start failure at bootup. Slim now starts, after
manual start of dbus.
GDM failure: Starts, but after taking a long time. I'll send Koop the log files
from my recent attempt.

You mentioned ghost text with nano in vt(4). Could you please file
a bug in Bugzilla with a picture of what you get? Please join a dmesg too.
I can confirm this is still an issue. I'll try to get to it at the soonest.

the unkillable processes are interesting. If you can reproduce
I really don't know how it came about, so no promises. The most interesting
part of that error however, was the behaviour of vt(4). The problem is not only
unkillable processes, but TTY freeze when doing an unrelated action to the
locked process. I mean, nano or top have nothing to do with webkit-gtk3, yet
caused TTY freeze (due to GPU lock-up I ignorantly presume)

the flickering you see with some applications/desktop environments
This is really serious. It has lessened, but not gone away.
Additionally, I started to get a sticky mouse problem some time ago
and I'm inclined to agree with HPS' assessment that drm2.ko graphics
driver has some hard spinning loops
(http://freebsd.1045724.n5.nabble.com/Some-unresolved-but-important-X-org-problems-td5987904.html)
Have not had the hardware to test with different GPU unfortunately.

Regards.
--
FreeBSD_amd64_11-Current_RadeonKMS
Please include my email when responding-I may have unabled auto-delivery.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

system failure: cannot kill webkit-gtk3 if using dumbell/radeon

2015-02-27 Thread Beeblebrox

I just hit a major kernel bug with the new Radeon code

* I'm on dumbbell's patch_38 for world/kernel (11.0-CURRENT #2 
45116d3(master)-dirty)
* I started www/midori and was getting segfaults with URL that start with h. 
I re-built midori using WITH_DEBUG=yes, got no output, then re-built without 
DEBUG enabled because I was having image display problems. Reported the problem 
as port issue: 
http://freebsd.1045724.n5.nabble.com/www-midori-dislikes-the-letter-h-td5992424.html
* At some point while using Midori (and right after I logged into Facebook) 
sytem started to hiccup and slow down, so I swithced to tty*. I start X.org 
with startx, so I tried to kill X with ctr+c  no response.

Here's where it gets interesting. Each step indicated with * was done on 
different tty, all tty's were logged in as root:
* issue # top  tty froze, does not exit.
* Several other simple root-level commands from different TTY result in TTY 
freeze.
* Let's free some RAM:
# service kill xyz  nothing, no result
kill -9 process-name  ok
jail -r aa bb cc  tty freeze
* jls  jails still running, previous command obviously could not kill
let's kill processes:
kill -9 process_num_for_midori  ok
kill -9 process_num_for_several others  ok
kill -9 process_num_for_WebKitWeb  NOPE, DOES NOT KILL
* # shutdown now  hangs for ever
* On TTY1: shows signal 15, but does not proceed. Seems to have
difficulty killing jails. ctl+alt+del helps a bit. Shuts down
eventually, after appx 10 mins.

After restart and in xorg, one cycle of start/stop for Midori does not produce 
any of symptoms above.
When killing WebKitWeb, the higher process_numbers died, but the lower 
process_numbers resisted. So the spawned processes could be killed, but the 
master process could not.

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

Re: system failure: cannot kill webkit-gtk3 if using dumbell/radeon

2015-02-27 Thread Beeblebrox

I see some errors in my last post, correcting:

I used # service onestop xyz and NOT # service kill xyz

One of the TTY freezes occurred when exiting nano: ctrl+x, y (exit  save)

-- 
FreeBSD_amd64_11-Current_RadeonKMS
Please include my email when responding (use Reply To All)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Some unresolved but important X.org problems

2015-02-11 Thread Beeblebrox

Hello.

 The drm2.ko graphics driver has some hard spinning loops, which may
 be the cause of the problems you are seeing and not
 actually /dev/ums0. Are any error messages printed in dmesg ?

I have all debug disabled in my kernel (no WITNESS, no GDB/DDB), so no 
messages. If you think it's worth wile, I'll build a fresh world and a full 
DEBUG enabled kernel or I could build graphics/drm with the debug option?

 evince crashes for me about 1 out of two but files with purely
 images seems to fare slightly better than others.
 people have pointed fingers in the general direction of gtk/cairo

I was one of those finger pointers as well, since all apps would display 
any/all text as little squares then immediately crash; unless cairo was 
specifically built with the WITH_DEBUG=yes option. IDK why that worked really, 
it just did.
 
 I'm running firefox 35 on current and that seems to be working OK.
I get same results as I described for Seamonkey.
 
 My guess is that your problems are specific to your graphics
 hardware, and therefore it could be valuable if you could try,
 just as an experiment, to move your diskdrive to different hardware,
 just to see if the problems comes along for the ride.
 
I have diskless environment set up and serving from a jail (NFS not jailed 
obviously), so I try your suggestion with any pxe_boot capable machine. 
Unfortunately the available clients are either RS780/RS880 family, have no GPU, 
or i386. I'll have to get creative to test your idea. However, I have 
corresponded with JS Pedron several times before, so he is aware of the 
issue(s) and he did not seem to think the problem was with Radeon drivers.

I also collected loud debug output in the past from the Kernel, without 
getting much of a result. Which makes me think the debug should be set for the 
application level and not the Kernel level. The problem is, how to log all that 
output from 5-10 different apps all at the same time? (plus would it be worth 
the exercise?)

Regards.

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

Some unresolved but important X.org problems

2015-02-11 Thread Beeblebrox

I have been having problems described below since March of 2014, but did not 
have much of an option other than to wait for gradual improvements. Considering 
that 11 is nearing official RELEASE, I would think these problems would be 
worth consideration. I'm posting in current rather than xorg, because if there 
were many others with these problems, it would have been brought up a long time 
ago.

PROBLEMS:
1. PDF viewers fail to display pdf/ps files correctly. Many files get displayed 
as blank pages, and I can only get the pdf to display after closing/re-opening 
the file several times, or by repeatedly scrolling up/down past the seemingly 
blank page. Pages with an image have more problems than pages with text-only.

2. With the exception of Opera (which is out-dated), all remaining Browsers 
fail to display most web pages in a sane manner (Firefox, Seamonkey, Epiphany, 
Midori). Chrome is the worst because even with just a blank page it flickers, 
goes completely white, comes back as a partial image and sometimes locks X for 
1/2 second or so.
Problems with the other browsers usually have something to do with sites using 
php (rather than static content) and I have many problems with images being 
correctly displayed. Among the symptoms:
* Page phases out. Mouse-over or scroll up/down resets the display 
(midori-on-linuxquestions.png: 
https://drive.google.com/file/d/0Bxs_eepbMt6qNTdaQm1pTFZTMWM/view?usp=sharing)
* PHP sites either loose track of last scroll point and jump appx one page up 
(example Facebook goes up 4-5 posts to what I just read and repeats action as I 
try to scroll down), OR they are only partially displayed and need to be either 
refreshed (F5) or up/down scrolling to get some kind of display 
(epiphany-on-forums.freebsd.png: 
https://drive.google.com/file/d/0Bxs_eepbMt6qbFJWMW1RZzJsYVU/view?usp=sharing)
* I get the same problem when trying to view an image, or a site with many 
images. The tab with the image displays one of: a black screen, a single color 
with vertical interference lines, or a mixture 
(seamonkey-google-image-search.png: 
https://drive.google.com/file/d/0Bxs_eepbMt6qUUJvem11U3c3MVk/view?usp=sharing)
* As a result of all the above, logging in to sites, doing any transactions 
which require clicking buttons and check-boxes or filling text fields becomes 
extremely difficult.

3. In Gnome3, menu text is garbled (gnome3-text.png: 
https://drive.google.com/file/d/0Bxs_eepbMt6qWklaSUZLd0luUFk/view?usp=sharing)

4. Chromium causes other programs to mis-behave and display gets corrupted in 
the old Win-XP style (chrome-corruption.png: 
https://drive.google.com/file/d/0Bxs_eepbMt6qMktnOWo3bV93SGM/view?usp=sharing)

5. An update about a month ago is causing problems with /dev/ums0 on Desktop 
(not vt). When I move the mouse it sometimes gets stuck on a menu item of a 
program or an item on the Browser (for example a result in google search). I 
have to move the mouse and repeat the previous action in order to get it 
unstuck. Sticky lasts about 1/5 of a second.

6. Last week I was getting jpeg file corruption when doing simple processing 
(crop, rotate) in graphics/gthumb. Resulting file would have vertical 
interference lines. After updating the ports/packages yesterday I don't get 
that now. Probably unrelated, but worth mentioning.

MY_SYSTEM:
+ Desktop is usually Fluxbox. Free Memory was 5 GB when screen shots were taken 
(not a low-mem issue).
+ GPU is RS880 [Radeon HD 4250], with loaded modules: drm2.ko, agp.ko, 
radeonkms.ko, radeonkmsfw_RS780_pfp.ko, radeonkmsfw_RS780_me.ko, 
radeonkmsfw_R600_rlc.ko
+ These already in /etc/sysctl.conf:
#_Enhance shared memory X11 interface
kern.ipc.shmmax=67108864
kern.ipc.shmall=32768
#_Enhance desktop responsiveness under high CPU use (200/224)
kern.sched.preempt_thresh=224
#_chromium_browser_issue
kern.ipc.shm_allow_removed=1

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

Re: Buildworld fails due to WITHOUT_CRYPT (3 issues)

2014-12-29 Thread Beeblebrox

 I fixed 2/3 of the issues in the following commits:
 1. https://svnweb.freebsd.org/changeset/base/276319
 3. https://svnweb.freebsd.org/changeset/base/276318

Thanks for the e-mail Garret. Before I proceed to file PR, I'd like some input 
as to what to do about these problems which I had mentioned in subsequent 
emails and which I can confirm persist after a fresh buildworld run (removed 
Herbert's patch) on Rev: 276354.

PROBLEM-1: ctld. Not shure how much CAM and ZFS are related. Not using anything 
CAM afaik, as netiher kernel (device ctl) nor loadr.conf have ctld. So I assume 
this is a no big deal level issue?
=== usr.sbin/ctld (all)
cc  -O2 -pipe   -I/asp/git/src/usr.sbin/ctld 
-I/asp/git/src/usr.sbin/ctld/../../sys 
-I/asp/git/src/usr.sbin/ctld/../../sys/cam/ctl 
-I/asp/git/src/usr.sbin/ctld/../../sys/dev/iscsi -DNDEBUG -std=gnu99 
-fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W 
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith 
-Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter 
-Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls 
-Wold-style-definition -Wno-pointer-sign -Wthread-safety -Wno-empty-body 
-Wno-string-plus-int -Wno-unused-const-variable -Qunused-arguments  -o ctld 
ctld.o discovery.o isns.o kernel.o keys.o log.o login.o parse.o pdu.o token.o  
-lbsdxml  -ll  -lsbuf  -lutil
discovery.o: In function `discovery_target_filtered_out':
/asp/git/src/usr.sbin/ctld/discovery.c:(.text+0x45b): undefined reference to 
`chap_authenticate'
login.o: In function `login':
/asp/git/src/usr.sbin/ctld/login.c:(.text+0x628): undefined reference to 
`chap_new'
/asp/git/src/usr.sbin/ctld/login.c:(.text+0x648): undefined reference to 
`chap_get_challenge'
/asp/git/src/usr.sbin/ctld/login.c:(.text+0x654): undefined reference to 
`chap_get_id'
/asp/git/src/usr.sbin/ctld/login.c:(.text+0x7a0): undefined reference to 
`chap_receive'
/asp/git/src/usr.sbin/ctld/login.c:(.text+0x7cc): undefined reference to 
`chap_authenticate'
/asp/git/src/usr.sbin/ctld/login.c:(.text+0x8e2): undefined reference to 
`rchap_new'
/asp/git/src/usr.sbin/ctld/login.c:(.text+0x8f3): undefined reference to 
`rchap_receive'
/asp/git/src/usr.sbin/ctld/login.c:(.text+0x903): undefined reference to 
`rchap_get_response'
/asp/git/src/usr.sbin/ctld/login.c:(.text+0x90e): undefined reference to 
`rchap_delete'
cc: error: linker command failed with exit code 1 (use -v to see invocation)
*** Error code 1

PROBLEM-2: MK_PKGBOOTSTRAP
=== usr.sbin/pkg (all)
cc  -O2 -pipe   -I/asp/git/src/usr.sbin/pkg/../../contrib/libucl/include 
-DNDEBUG -std=gnu99 -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W 
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith 
-Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter 
-Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls 
-Wold-style-definition -Wno-pointer-sign -Wmissing-variable-declarations 
-Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable 
-Qunused-arguments -c /asp/git/src/usr.sbin/pkg/pkg.c
/asp/git/src/usr.sbin/pkg/pkg.c:54:10: fatal error: 'openssl/err.h' file
  not found
#include openssl/err.h

PROBLEM-3: No /usr/sbin/mtree after # installworld

Other than these 3, there's also the persistent problem involving ccache, which 
again is no big deal, just FYI.

Regards

-- 
FreeBSD_amd64_11-Current_RadeonKMS


pgpS5A799pkd7.pgp
Description: OpenPGP digital signature

Buildworld fails due to WITHOUT_CRYPT (3 issues)

I plan on using openssl from ports and have no need for kerberos.
/etc/src.conf  WITHOUT_CRYPT= yes

* First problem is with bsnmp (used WITHOUT_BSNMP to bypass)
=== lib/libbsnmp/libbsnmp (all)
cc   -O2 -pipe   
-I/asp/git/src/lib/libbsnmp/libbsnmp/../../../contrib/bsnmp/lib -DHAVE_ERR_H 
-DHAVE_GETADDRINFO -DHAVE_STRLCPY -DHAVE_STDINT_H -DHAVE_INTTYPES_H 
-DQUADFMT='llu' -DQUADXFMT='llx' -DNDEBUG -std=gnu99 -fstack-protector 
-Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter 
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type 
-Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align 
-Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls 
-Wold-style-definition -Wno-pointer-sign -Wmissing-variable-declarations 
-Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable 
-Qunused-arguments -c 
/asp/git/src/lib/libbsnmp/libbsnmp/../../../contrib/bsnmp/lib/snmpcrypto.c -o 
snmpcrypto.o
/asp/git/src/lib/libbsnmp/libbsnmp/../../../contrib/bsnmp/lib/snmpcrypto.c:370:1:
 error: 
  conflicting types for 'snmp_passwd_to_keys'
snmp_passwd_to_keys(struct snmp_user *user, char *passwd __unused)
/asp/git/src/lib/libbsnmp/libbsnmp/../../../contrib/bsnmp/lib/snmp.h:273:16: 
note: 
  previous declaration is here
enum snmp_code snmp_passwd_to_keys(struct snmp_user *, char *);
/asp/git/src/lib/libbsnmp/libbsnmp/../../../contrib/bsnmp/lib/snmpcrypto.c:382:1:
 error: 
  conflicting types for 'snmp_get_local_keys'
snmp_get_local_keys(struct snmp_user *user, uint8_t *eid __unused,
/asp/git/src/lib/libbsnmp/libbsnmp/../../../contrib/bsnmp/lib/snmp.h:274:16: 
note: 
  previous declaration is here
enum snmp_code snmp_get_local_keys(struct snmp_user *, uint8_t *, uint32_t);

* Second problem is with ldns (used WITHOUT_LDNS as temporary fix)
=== lib/libldns (all)
/usr/local/libexec/ccache/world/clang -target x86_64-unknown-freebsd11.0  -O2 
-pipe   -I/asp/git/src/lib/libldns/../../contrib/ldns -DNDEBUG -std=gnu99 
-fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W 
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith 
-Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int 
-Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value 
-Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion 
-Qunused-arguments -c /asp/git/src/lib/libldns/../../contrib/ldns/buffer.c -o 
buffer.o
In file included from /asp/git/src/lib/libldns/../../contrib/ldns/buffer.c:12:
In file included from 
/asp/git/src/lib/libldns/../../contrib/ldns/ldns/ldns.h:98:
/asp/git/src/lib/libldns/../../contrib/ldns/ldns/dane.h:31:10: fatal error: 
  'openssl/ssl.h' file not found
#include openssl/ssl.h

* I found no work-around for this problem so I'm now stuck.
=== lib/libc/tests/hash (depend)
(cd /asp/git/src/lib/libc/tests/hash  make -f 
/asp/git/src/lib/libc/tests/hash/Makefile _RECURSING_PROGS=  SUBDIR= 
PROG=h_hash  DEPENDFILE=.depend.h_hash .MAKE.DEPENDFILE=.depend.h_hash   depend)
(cd /asp/git/src/lib/libc/tests/hash  make -f 
/asp/git/src/lib/libc/tests/hash/Makefile _RECURSING_PROGS=  SUBDIR= 
PROG=sha2_test  DEPENDFILE=.depend.sha2_test .MAKE.DEPENDFILE=.depend.sha2_test 
  depend)
rm -f .depend.sha2_test
CC='/usr/local/libexec/ccache/world/clang -target x86_64-unknown-freebsd11.0 ' 
mkdep -f .depend.sha2_test -a
-I/asp/git/src/lib/libc/tests/hash/../../../../crypto/openssh/openbsd-compat 
-I/asp/git/src/lib/libc/tests/hash/../../../../crypto/openssh 
-I/asp/git/src/lib/libnetbsd -I/asp/git/src/contrib/netbsd-tests -DNDEBUG 
-std=gnu99   /asp/git/src/contrib/netbsd-tests/lib/libc/hash/t_sha2.c
/asp/git/src/contrib/netbsd-tests/lib/libc/hash/t_sha2.c:45:10: fatal error: 
  'openssl/sha.h' file not found

* I would prefer being able to use SSH from world (instead of dropbear), but 
that seems impossible when openssl is disabled.

* Different question, but when doing buildworld for i386 (buildworld 
TARGET=i386) I try CCACHE_DISABLE=yes or -DNO_CCACHE. Both alternatives seem to 
be ignored, because of the output I see scrolling by (all lines begin with 
/usr/local/libexec/ccache/world/clang). Is this as expected or am I doing it 
wrong?

Regards.
-- 
FreeBSD_amd64_11-Current_RadeonKMS
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Buildworld fails due to WITHOUT_CRYPT (3 issues)


 Instead of using WITHOUT_CRYPT, you could have used WITHOUT_KERBEROS.
I know that, but I don't want to waste time compiling openssl either.

 You can still install openssl from ports.
Thanks. As stated it's just a matter of not wanting to compile something I'm 
not going to use.

 What's wrong with security/openssh-portable?
Nothing, I just gave dropbear as an example. This port would be preferable of 
course.

I re-started buildworld after re-enabling all crypto modules (incl
krb5) and it's now breaking at telnet:
=== libexec/telnetd (all)
cc  -O2 -pipe   -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON  -DENV_HACK 
-DSTREAMSPTY -I/asp/git/src/libexec/telnetd/../../contrib/telnet 
-I/asp/git/src/libexec/telnetd/../../contrib/telnet/telnet -DAUTHENTICATION 
-DENCRYPTION -DKRB5 -DFORWARD -Dnet_write=telnet_net_write -DNDEBUG -std=gnu99 
-fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized 
-Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int 
-Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value 
-Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-switch 
-Wno-switch-enum -Wno-knr-promoted-parameter -Qunused-arguments  -o telnetd 
global.o slc.o state.o sys_term.o telnetd.o termstat.o utility.o authenc.o 
-L/usr/obj/asp/git/src/lib/libtelnet -ltelnet  -lutil  -lncursesw  -lmp  
-lcrypto  -lpam  -lkrb5   -lroken -lpthread
/usr/obj/asp/git/src/lib/libtelnet/libtelnet.a(auth.o): In function `auth_name':
/asp/git/src/lib/libtelnet/../../contrib/telnet/libtelnet/auth.c:(.text+0x9d5): 
undefined reference to `auth_encrypt_user'
/usr/obj/asp/git/src/lib/libtelnet/libtelnet.a(sra.o): In function `sra_is':
/asp/git/src/lib/libtelnet/../../contrib/telnet/libtelnet/sra.c:(.text+0x290): 
undefined reference to `auth_encrypt_user'
cc: error: linker command failed with exit code 1 (use -v to see invocation)

Herbert: I'm going to have to delete the whole compiled mess and re-start. I'll 
apply your patch and advise the results.

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

Re: Buildworld fails due to WITHOUT_CRYPT (3 issues)

I patched Herbert's code, deleted the entire partial world and have 
WITHOUT_CRYPT, WITHOUT_BSNMP in src.conf.

First this part below broke, but managed to move forward when I disabled ccache 
(clipped for brevity):
=== rescue/rescue/chown/tests (depend)
(cd /asp/git/src/usr.sbin/chown/tests  make -f 
/asp/git/src/usr.sbin/chown/tests/Makefile SUBDIR= _RECURSING_PROGS=  depend)
`chown.o' is up to date.
nc.lo: In function `_$$hide$$ nc.lo main':
(.text+0x61a): warning: warning: mktemp() possibly used unsafely; consider 
using mkstemp()
/usr/lib/libarchive.a(archive_crypto.o): In function 
`__archive_openssl_md5init':
/asp/git/src/lib/libarchive/../../contrib/libarchive/libarchive/archive_crypto.c:(.text+0xa):
 undefined reference to `EVP_md5'
/asp/git/src/lib/libarchive/../../contrib/libarchive/libarchive/archive_crypto.c:(.text+0x15):
 undefined reference to `EVP_DigestInit'
..
/usr/lib/libarchive.a(archive_crypto.o): In function 
`__archive_openssl_sha512init':
/asp/git/src/lib/libarchive/../../contrib/libarchive/libarchive/archive_crypto.c:(.text+0x1ba):
 undefined reference to `EVP_sha512'
/asp/git/src/lib/libarchive/../../contrib/libarchive/libarchive/archive_crypto.c:(.text+0x1c5):
 undefined reference to `EVP_DigestInit'
/usr/lib/libarchive.a(archive_crypto.o): In function 
`__archive_openssl_sha512update':
/asp/git/src/lib/libarchive/../../contrib/libarchive/libarchive/archive_crypto.c:(.text+0x1e5):
 undefined reference to `EVP_DigestUpdate'
/usr/lib/libarchive.a(archive_crypto.o): In function 
`__archive_openssl_sha512final':
/asp/git/src/lib/libarchive/../../contrib/libarchive/libarchive/archive_crypto.c:(.text+0x1f7):
undefined reference to `EVP_DigestFinal'

* Then LDNS broke again, so I disabled that once more:
=== lib/libldns (all)
make[5]: /usr/obj/asp/git/src/lib/libldns/.depend, 2187: ignoring stale .depend 
for /usr/obj/asp/git/src/tmp/usr/lib/libcrypto.a
building shared library libldns.so.5
/usr/obj/asp/git/src/tmp/usr/bin/ld: cannot find -lcrypto

* Finally buildworld broke at CAM
=== usr.sbin/ctld (all)
cc  -O2 -pipe   -I/asp/git/src/usr.sbin/ctld 
-I/asp/git/src/usr.sbin/ctld/../../sys 
-I/asp/git/src/usr.sbin/ctld/../../sys/cam/ctl 
-I/asp/git/src/usr.sbin/ctld/../../sys/dev/iscsi -DNDEBUG -std=gnu99 
-fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W 
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith 
-Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter 
-Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls 
-Wold-style-definition -Wno-pointer-sign -Wthread-safety -Wno-empty-body 
-Wno-string-plus-int -Wno-unused-const-variable -Qunused-arguments -c 
/asp/git/src/usr.sbin/ctld/chap.c
/asp/git/src/usr.sbin/ctld/chap.c:38:10: fatal error: 'openssl/err.h' file not
  found
#include openssl/err.h
That file has several: (#include openssl/err.h, #include openssl/md5.h, 
#include openssl/rand.h). Other that deleting the include lines, how should I 
disable those?

* At svn revision 276177

Wow I haven't had this much trouble for quite a while. I don't see a full moon, 
so it must be because of the way the planets are aligned today :(

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

Re: Buildworld fails due to WITHOUT_CRYPT (3 issues)

* So as to keep the build going, I commented out ctld in the usr.sbin/Makefile

* The next part to break was pkg. I set WITHOUT_PKGTOOLS, but that did
  not solve the problem, so I once more had to comment out in
  usr.sbin/Makefile SUBDIR+= pkg
=== usr.sbin/pkg (all)
cc  -O2 -pipe   -I/asp/git/src/usr.sbin/pkg/../../contrib/libucl/include 
-DNDEBUG -std=gnu99 -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W 
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith 
-Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter 
-Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls 
-Wold-style-definition -Wno-pointer-sign -Wmissing-variable-declarations 
-Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable 
-Qunused-arguments -c /asp/git/src/usr.sbin/pkg/pkg.c
/asp/git/src/usr.sbin/pkg/pkg.c:54:10: fatal error: 'openssl/err.h' file not 
found
#include openssl/err.h

* Buildworld finally finished, but admittedly it's plain ugly. I decided to 
post the last the process so as to help anyone who might have a similar 
experience. Whether the CRYPT code should be used from base or ports is 
debatable, but BASE does not seem ready for complete switch for these functions 
from /src to /ports.

Regards.
-- 
FreeBSD_amd64_11-Current_RadeonKMS
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Buildworld fails due to WITHOUT_CRYPT (3 issues)

So far from what I can tell, two modules don't get built for some reason.

* sys/boot/i386/boot2
I built and installed this manually:

* usr/sbin/mtree
This is missing, and usr.sbin/mtree gives fmtree. Trying
from contrib/mtree results in:
/usr/local/libexec/ccache/world/clang -O2 -pipe   -DNDEBUG -std=gnu99 
-fstack-protector   -Qunused-arguments -c compare.c
compare.c:61:10: fatal error: 'rmd160.h' file not found
#include rmd160.h

That file seems to be one of sys/opencrypto/rmd160.h or lib/libnetbsd/rmd160.h, 
but at this point I'm stumped. Did this have anything to do with Herbert's 
patch? 
I had cleaned out my poudriere amd64 jail, and mtree is needed for pkg 
building. I finally resorted to copying the two-week old mtree binary from 
/usr/sbin to the poudriere jail.

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

Kernel now detecting cpu core faults? Two thumbs up.

2014-12-10 Thread Beeblebrox

My CPU shows as: AMD Phenom II X4 B60 Processor (3671.47-MHz), But in fact it's 
an X3-B60, with the 4th core unlocked by the BIOS.

I was running poudriere today and dmesg gave this message:

MCA: Bank 1, Status 0x94000151
MCA: Global Cap 0x0106, Status 0x
MCA: Vendor AuthenticAMD, ID 0x100f53, APIC ID 3
MCA: CPU 3 COR ICACHE L1 IRD error
MCA: Address 0x801cb2ca0

That's just awesome! The kernel now warns of problems on faulty core (which is 
why my CPU is an X4, priced and sold as X3).

#2 r275010

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

Re: r273918 buildworld broke at semaphore

2014-11-14 Thread Beeblebrox

I posted the solution to this through the Nabble page, but there's a 
change in setting there and the messages have not gone through. So, 
re-posting to mail list:


I disabled ccache, then buildworld / buildkernel completed.

I had in /etc/make.conf:
.if ${.CURDIR:M/usr/src} || ${.CURDIR:M/usr/src/*} || 
${.CURDIR:M/asp/git/src} || ${.CURDIR:M/asp/git/src/*}

THREADS=16
#CC:=${CC:C,^cc,/usr/local/libexec/ccache/world/clang,1}
#CXX:=${CXX:C,^c\+\+,/usr/local/libexec/ccache/world/clang++,1}

The only reason I can think of is that somehow ccache was passing the 
older cached code to the buildworld process, and the reason for that 
wold be because certain clang components fail to identify themselves to 
ccache correctly.


Once I installed the newly built kernel/world and re-booted
* I deleted all under /usr/obj
* re-enabled ccache in make.conf
* re-ran # make buildworld  completed without problem.

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

Is libLLVM-3.4.so: part of src or not?

2014-11-14 Thread Beeblebrox


When starting Xorg, AIGLX gets disabled and RadeonKMS complains:

(EE) AIGLX error: dlopen of /usr/local/lib/dri/r600_dri.so failed 
(Shared object libLLVM-3.4.so n

ot found, required by r600_dri.so)
(EE) AIGLX: reverting to software rendering
(II) AIGLX: Screen 0 is not DRI capable
(EE) AIGLX error: dlopen of /usr/local/lib/dri/swrast_dri.so failed 
(Shared object libLLVM-3.4.so

 not found, required by swrast_dri.so)
(EE) GLX: could not load software renderer
(II) GLX: no usable GL providers found for screen 0

A search on the system shows libLLVM-3.4.so only exists under 
/usr/local/lib32.
I built and installed devel/llvm34, re-started Xorg and the log shows 
AIGLX as starting normally (no error).


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

Re: r273918 buildworld broke at semaphore

2014-11-12 Thread Beeblebrox

I solved this problem about 4 hours ago and posted through the Nabble 
interface.


My email is not posting to the mail list, and stil shows as 
not-accepted - there's some sort of problem there...


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

Re: r273918 buildworld broke at semaphore

2014-11-11 Thread Beeblebrox


Seems like your tree is not fully up to date?  The changes to
sem_new.c were
committed in the same commit as the changes to sys/umtx.h.


I deleted the entire contents of /usr/src, then did
# svn co svn://svn.freebsd.org/base/head
Buildworld breaks at same place (semaphore)

This error AFAIK, was already combined with:
http://freebsd.1045724.n5.nabble.com/r273910-build-failure-if-lt-sys-umtx-h-gt-is-out-of-date-td5961186.html

Speaking of out-of-date,
http://freebsd.1045724.n5.nabble.com/version-number-error-with-ports-td5961642.html

Regards.

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

Re: r273910 build failure if sys/_umtx.h is out-of-date

2014-11-03 Thread Beeblebrox


I was just curious and decided to try an i386 build:
# make -C /usr/src buildworld TARGET=i386 -DNO_CCACHE
Gives same error:

/asp/git/src/lib/libc/../../include/semaphore.h:41:16: error: field has 
incomplete type 'struct _usem2'

struct _usem2   _kern;  ^
/asp/git/src/lib/libc/../../include/semaphore.h:41:9: note: forward 
declaration

of 'struct _usem2'
struct _usem2   _kern;   ^
cancelpoints_sem_new.c:66:33: error: use of undeclared identifier 
'USEM_MAX_COUNT'
_Static_assert(SEM_VALUE_MAX = USEM_MAX_COUNT, SEM_VALUE_MAX too 
large);^
cancelpoints_sem_new.c:335:15: warning: implicit declaration of function 
'USEM_COUNT' is invalid in C99 [-Wimplicit-function-declaration]

*sval = (int)USEM_COUNT(sem-_kern._count);   ^
cancelpoints_sem_new.c:342:23: error: use of undeclared identifier 
'UMTX_OP_SEM2_WAKE'

return _umtx_op(sem, UMTX_OP_SEM2_WAKE, 0, NULL, NULL);   ^
cancelpoints_sem_new.c:361:23: error: use of undeclared identifier 
'UMTX_OP_SEM2_WAIT'

return _umtx_op(sem, UMTX_OP_SEM2_WAIT, 0,^
cancelpoints_sem_new.c:445:14: error: use of undeclared identifier 
'USEM_HAS_WAITERS'

if (count  USEM_HAS_WAITERS)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

version number error with ports

2014-11-01 Thread Beeblebrox

There seems to be a problem with certain ports detecting the OS version.

* This happens with emulators/i386-wine-devel; it's unable to detect the
version and exits.

* Poudriere shows below message:
make: /usr/ports/Mk/bsd.port.mk line 1216: warning: /usr/bin/awk
'/^#define[[:blank:]]__FreeBSD_version/ {print $3}' 
/usr/include/sys/param.h exited on a
signal
make: /usr/ports/Mk/bsd.port.mk line 1228: UNAME_r (11.0-CURRENT) and
OSVERSION () do not agree on major version number.

uname  FreeBSD 11.0-CURRENT #0 r272601M: Mon Oct  6 ... amd64
Will upgrade as soon as recent buildworld / clang error is fixed.



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/version-number-error-with-ports-tp5961642.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

r273918 buildworld broke at semaphore

2014-10-31 Thread Beeblebrox

First breakage in a long time. Error is:

In file included from cancelpoints_sem_new.c:47:
/usr/src/lib/libc/../../include/semaphore.h:41:16: error: field has
incomplete type 'struct _usem2'
struct _usem2   _kern;
^
/usr/src/lib/libc/../../include/semaphore.h:41:9: note: forward declaration
of 'struct _usem2'
struct _usem2   _kern;
   ^
cancelpoints_sem_new.c:66:33: error: use of undeclared identifier
'USEM_MAX_COUNT'
_Static_assert(SEM_VALUE_MAX = USEM_MAX_COUNT, SEM_VALUE_MAX too large);
^
cancelpoints_sem_new.c:335:15: warning: implicit declaration of function
'USEM_COUNT' is invalid in C99 [-Wimplicit-function-declaration]
*sval = (int)USEM_COUNT(sem-_kern._count);
 ^
cancelpoints_sem_new.c:342:23: error: use of undeclared identifier
'UMTX_OP_SEM2_WAKE'
return _umtx_op(sem, UMTX_OP_SEM2_WAKE, 0, NULL, NULL);
 ^
cancelpoints_sem_new.c:361:23: error: use of undeclared identifier
'UMTX_OP_SEM2_WAIT'
return _umtx_op(sem, UMTX_OP_SEM2_WAIT, 0,
 ^
cancelpoints_sem_new.c:445:14: error: use of undeclared identifier
'USEM_HAS_WAITERS'
if (count  USEM_HAS_WAITERS)
^
1 warning and 5 errors generated.




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/r273918-buildworld-broke-at-semaphore-tp5961241.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: r273910 build failure if sys/_umtx.h is out-of-date

2014-10-31 Thread Beeblebrox

Hello

 Beeblebrox should confirm whether or not he’s using gcc in the build
 or clang. Thanks!

Using clang
I have some tighter settings in src.conf, but nothing clang/gcc related.

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

Re: r273910 build failure if sys/_umtx.h is out-of-date

2014-10-31 Thread Beeblebrox

 Hi!
   Do you have WITHOUT_CLANG_BOOTSTRAP set?
 Thanks!

No.
No clang/gcc settings. All src.conf WITHOUT entries are of the sort 
INET6, PORTSNAP, BLUETOOTH, etc

I DO use ccache

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

Re: Some NFS server V4 questions

2014-10-26 Thread Beeblebrox

Sorry guys, we have a considerable time-zone difference.

 It appears that the sysctl must be set before mountd, nfsd are
 started to take effect. (Or they must be restarted after it is set.)
I had apparently re-started nfsd but not mountd. This time re-starting both and 
launching the PXE client fails at mount_root stage as expected:
exec /sbin/init: error 43
exec /rescue/init: error 43
panic: no init

One cannot set sysctl vfs.nfsd.server_min_nfsvers=4 until one of mountd/nfsd 
is started however, otherwise it gives an error. I have not tried, but I 
suppose this error does not happen when placeed in /etc/sysctl.conf?
sysctl: unknown oid 'vfs.nfsd.server_min_nfsvers': No such file or directory

 Maybe it was the talk about getting rid of the oldnfs stuff that
 made you think V2, 3 were going away?
Yes, that was it and I obviously misunderstood that thread.

What's the max NFS version that supports mount_root from PXE clients then? As I 
recall, this would be V3. However, root is consistently being mounted as V2.
The fstab for diskless clients:
192.168.2.1:/data/amd64 /   nfs ro,nfsv30  0
192.168.2.1:/usr/local /usr/local nfs   ro,nfsv40  0
192.168.2.1:/home   /home   nfs rw,nfsv4,hard,intr  0  0

nfsstat shows / as NFSV2, while the other two are NFSV4. Changing fstab entry 
to nfsv4 for root gives same result.
I tried set sysctl vfs.nfsd.server_min_nfsvers=3 and I get the same 
mount_root error as when this was set to 4. Im I missing something? It does not 
seem that vfs.nfsd.server_min_nfsvers will be of much use to me, unless I can 
get  V2 to mount as root.

Regards.




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp5959433p5959595.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Some NFS server V4 questions

2014-10-26 Thread Beeblebrox

Dan:
 to get pxeboot to do v3, add to /boot/loader.conf
 boot-nfsroot-options=“nfsv3”
Thanks. I'm using grub for the bootloader and menu, and comparable entry should 
be:
set kfreebsd.boot.nfsroot.options=nfsv3
It does not work however. mount_root hangs for a while then reverts to V2. I've 
asked about this on the grub-devel list, and will share the answer here.

Rick:
Would it be worth trying to pass a nolockd option for this? As you had stated 
in another thread,
For NFSv3 mounts, I'd suggest the nolockd option, unless you have multiple 
clients concurrently doing byte range locking on the same file. (With nolockd 
option on the mounts, you shouldn't need to run rpc.lockd, rpc.statd and that 
implies NFSLOCKD shouldn't be needed, too.)
Should I try this? If yes, how is it done?

 Just fyi, hard is the default and intr is an alternative to hard, so 
 I'm not sure what you get when specifying both? You should choose one or the 
 other. (You will get hard for the first 2 entries.)
Thanks. Corrected by removing both.

Konstantin:
Have not gotten around to trying the code yet and thanks.




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp5959433p5959686.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: HEADS UP: Merging projects/bhyve_svm to HEAD

2014-10-26 Thread Zaphod Beeblebrox

I would be using such a patch as soon as it was available.  On a friend's
advice, I upgraded a ZFS server here at home with an AMD 9590 and 32Gig of
RAM.  I'd dearly like to use it to track down the netgraph bug (see my
other recent posts), but it doesn't currently qualify.

On Sat, Oct 25, 2014 at 8:20 PM, Neel Natu neeln...@gmail.com wrote:

 Hi,

 On Sat, Oct 25, 2014 at 3:50 PM, Zaphod Beeblebrox zbee...@gmail.com
 wrote:
  I tried to integrate this patch into 10.1_RC3 and I failed.  Is there a
  timeframe to MFC this to 10.1 or 10-STABLE?
 

 It will be MFCed to 10-STABLE but I don't have a specific time frame in
 mind.

 I'll guess that it'll be towards the end of November but can be
 accelerated if someone has a need for this in 10-STABLE sooner.

 best
 Neel

  On Sun, Oct 19, 2014 at 4:04 PM, Benjamin Perrault 
 ben.perra...@gmail.com
  wrote:
 
  After a few days of extensive testing and abuse, i’ve run into no new
  issues or unknowns what so ever. Everything that worked before still
 works
  now ( and a few bugs from fixed from HEAD ).
 
  Thus, I have gone ahead and pushed r273182 w/ Neel’s patch out to about
 80
  of the assorted AMD boxes in the production and dev pods that I care
 for. If
  end users see something, I’ll let you know, but I have a feeling they
 won’t.
 
  Again - Excellent work.
 
  cheers,
  -bp
 
   On Oct 19, 2014, at 5:03 AM, Willem Jan Withagen w...@digiware.nl
   wrote:
  
   On 16-10-2014 5:00, Anish Gupta wrote:
   Hi all,
  
   The projects/bhyve_svm branch is ready to be merged to HEAD.
  
   This branch contains patches to bhyve to enable it to work on AMD
   processors with SVM/AMD-V hardware extensions[1]. Pretty much any AMD
   processor since 2010 will have the features required by bhyve.
  
   bhyve on AMD supports (almost) all the features available with Intel
   [2]. All guest OSes supported on Intel are supported on AMD. All the
   bhyve-related utilities function similarly on both Intel and AMD
   platforms [3].
  
   The patch against HEAD revision 273066 is available for review and
   testing:
   https://people.freebsd.org/~neel/bhyve/bhyve_svm.diff [Neel’s web
   directory]
  
   [1]: http://en.wikipedia.org/wiki/X86_virtualization
   [2]: bhyve doesn't support PCI passthru on AMD at this time
   [3]: bhyvectl has grown some processor-specific options
  
   Fetched the patch and compiled.
   Now running: HEAD r273066M and I was able to throw at it all the tests
   and images that in the past works. And perhaps even better.
  
   Great work.
   --WjW
  
  
   ___
   freebsd-virtualizat...@freebsd.org mailing list
   http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
   To unsubscribe, send any mail to
   freebsd-virtualization-unsubscr...@freebsd.org
 
  ___
  freebsd-current@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-current
  To unsubscribe, send any mail to 
 freebsd-current-unsubscr...@freebsd.org
 
 

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

Some NFS server V4 questions

2014-10-25 Thread Beeblebrox

* I can't get the NFS server to run V4 only. I have:
sysctl vfs.nfsd.server_min_nfsvers=4

I start all NFS-related services manually (from script)
#!/bin/sh
rpcbind -s -h 192.168.2.1
mountd -rnl -h 192.168.2.1
nfsd -ut -n 4 -h 192.168.2.1
nfsuserd

/etc/exports has:
V4:  / -network 192.168.2.0/26
/data/amd64  /data/amd64/boot/s386-ro -network 192.168.2.0/26
/usr/local  -ro -maproot=0  -network 192.168.2.0/26
/home   -network 192.168.2.0/26

Running nfsstat -m from a PXE client gives me:
192.168.2.1:/data/amd64 on /
nfsv2,tcp,resvport,hard,cto,lockd,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=8192,wsize=8192,readdirsize=8192,readahead=1,wcommitsize=1997092,timeout=120,retrans=2
192.168.2.1:/home on /home
nfsv3,tcp,resvport,hard,intr,cto,lockd,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=65536,wsize=65536,readdirsize=65536,readahead=1,wcommitsize=1997092,timeout=120,retrans=2
192.168.2.1:/usr/local on /usr/local
nfsv3,tcp,resvport,hard,cto,lockd,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=65536,wsize=65536,readdirsize=65536,readahead=1,wcommitsize=1997092,timeout=120,retrans=2

The PXE-booted kernel is compiled with: nfscommon, nfssvc, nfs, nfscl,
nfslock
On server side, in addition to the above, these are loaded as modules:
acl_nfs4.ko, nfsd.ko, nfslockd.ko

PXE client's /etc/rc.conf the only NFS-related entry is:
nfs_client_enable=YES

PXE client's /etc/fstab is:
92.168.2.1:/data/amd64 /   nfs ro  0   0
192.168.2.1:/usr/local /usr/local nfs   ro  0   0
192.168.2.1:/home   /home   nfs rw,hard,intr0  0


* Considering V2/V3 for NFS is getting dropped from code base, PXE clients
used to need max V3 as root and could not mount_root with V4. Has this
changed? If so, what services do the clients need to get V4 on root working
(RO, no RW)?

* There was a simple command to show from server-side what version of NFS
the exports were running, but I seem to have lost that. Any clues?

* Have any of these services become capable of running from inside a jail
environment? {rpcbind mountd nfsd nfsuserd} - it does not seem so, but just
checking.

Thanks and Regards.



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp5959433.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Some NFS server V4 questions

2014-10-25 Thread Beeblebrox

Hi Russ,

  PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 /   nfs
  ro  0   0 192.168.2.1:/usr/local /usr/local nfs   ro  0
 
 Possibly need to arrange for mount_nfs to see -o nfsv4
 (I use mount_nfs -o nfsv4,minorversion=1)
Yeah, that would work very likely and thanks.

From a purist standpoint, what would be settings on server side to force NFSV4 
offering only? This means, how can I configure NFS so that V2/V3 requests get 
denied AND logged for debug?







-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp5959433p5959475.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: HEADS UP: Merging projects/bhyve_svm to HEAD

2014-10-25 Thread Zaphod Beeblebrox

I tried to integrate this patch into 10.1_RC3 and I failed.  Is there a
timeframe to MFC this to 10.1 or 10-STABLE?

On Sun, Oct 19, 2014 at 4:04 PM, Benjamin Perrault ben.perra...@gmail.com
wrote:

 After a few days of extensive testing and abuse, i’ve run into no new
 issues or unknowns what so ever. Everything that worked before still works
 now ( and a few bugs from fixed from HEAD ).

 Thus, I have gone ahead and pushed r273182 w/ Neel’s patch out to about 80
 of the assorted AMD boxes in the production and dev pods that I care for.
 If end users see something, I’ll let you know, but I have a feeling they
 won’t.

 Again - Excellent work.

 cheers,
 -bp

  On Oct 19, 2014, at 5:03 AM, Willem Jan Withagen w...@digiware.nl
 wrote:
 
  On 16-10-2014 5:00, Anish Gupta wrote:
  Hi all,
 
  The projects/bhyve_svm branch is ready to be merged to HEAD.
 
  This branch contains patches to bhyve to enable it to work on AMD
  processors with SVM/AMD-V hardware extensions[1]. Pretty much any AMD
  processor since 2010 will have the features required by bhyve.
 
  bhyve on AMD supports (almost) all the features available with Intel
  [2]. All guest OSes supported on Intel are supported on AMD. All the
  bhyve-related utilities function similarly on both Intel and AMD
  platforms [3].
 
  The patch against HEAD revision 273066 is available for review and
 testing:
  https://people.freebsd.org/~neel/bhyve/bhyve_svm.diff [Neel’s web
 directory]
 
  [1]: http://en.wikipedia.org/wiki/X86_virtualization
  [2]: bhyve doesn't support PCI passthru on AMD at this time
  [3]: bhyvectl has grown some processor-specific options
 
  Fetched the patch and compiled.
  Now running: HEAD r273066M and I was able to throw at it all the tests
  and images that in the past works. And perhaps even better.
 
  Great work.
  --WjW
 
 
  ___
  freebsd-virtualizat...@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
  To unsubscribe, send any mail to 
 freebsd-virtualization-unsubscr...@freebsd.org

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

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

Re: ZFS: i/o error - all block copies unavailable #2

2014-10-23 Thread Beeblebrox

You might want to try from the mfsbsd.iso  environment,
1. Import and mount the zpool you want to boot from
2. Copy /boot/zfs/zpool.cache to /mnt/boot/zfs/ (over-write existing
zpool.cache file)
3. Edit /mnt/boot/loader.conf and add any of these that you don't already
have:
zfs_load=YES
opensolaris_load=YES
vfs.root.mountfrom=zfs:zroot_name
zpool_cache_load=YES
zpool_cache_type=/boot/zfs/zpool.cache
zpool_cache_name=/boot/zfs/zpool.cache

Might be worth a try.



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/ZFS-i-o-error-all-block-copies-unavailable-2-tp5958692p5958899.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: printing text file with LPD - non-printable characters

Enscript does not support UTF-8 formatted text files, so it's not usable in
this case.

One solution, is to use paps, instead of Enscript, for converting UTF-8
encoded text to PostScript.
http://www.linuxfromscratch.org/blfs/view/svn/pst/enscript.html

Another (which I prefer) solution is to send to printer like this (with n
being the 8859 extension number):
$ iconv -f UTF-8 -t ISO-8859-n file-UTF8.txt | enscript --encoding=8859n |
lpr -Pprinter

Thanks to Martin Paredes for this suggestion.

Perhaps this information or the appropriate enscript conversion code for
psif could be included in the Handbook
(https://www.freebsd.org/doc/handbook/printing-lpd.html 10.5.3.4 /
10.5.3.5)?

Regards.



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/printing-text-file-with-LPD-non-printable-characters-tp5954561p5956648.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: printing text file with LPD - non-printable characters

 We are using in production environments CUPS in the version 1.4.3;
 this has a component 'texttops' which supports UTF-8 encoded text
 (only) and prints UTF-8 nicely on the fly.

Thanks for the input.
Unfortunately, CUPS has been broken for me since May/14.
(http://freebsd.1045724.n5.nabble.com/print-cups-base-web-interface-broken-amp-unable-to-print-td5918098.html#a5922974)

Installed CUPS components:
cups-base-1.7.3_1, cups-client-1.7.3_2, cups-image-1.7.3_1, cups-pdf-2.6.1_1, 
cups-pstoraster-8.15.4_8, gutenprint-cups-5.2.10

Regards.




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/printing-text-file-with-LPD-non-printable-characters-tp5954561p5956658.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: printing text file with LPD - non-printable characters

@Matthias:
 This is one of the reasons we stick with 1.4.3.

How? Did you create a self-maintained port for it?
How did you overcome the problem of CUPS-dependent ports pulling in 1.7.3 in 
poudriere?

Regards.




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/printing-text-file-with-LPD-non-printable-characters-tp5954561p5956672.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: printing text file with LPD - non-printable characters

@Don:

 I think it (cups) also broke for me around that timeframe until I
 found that I also needed cups-filters.

You sir, are a life saver! Thank you for the tip.
[SOLVED]




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/printing-text-file-with-LPD-non-printable-characters-tp5954561p5956782.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

printing text file with LPD - non-printable characters

2014-10-05 Thread Beeblebrox

I have two LPD errors
1. I see two characters being replaced by strings on the hard copy (the {â}
below is an {a^}). This happens on the first page and not on following
pages.
instead of  I get:  â\200\234 (235 for trailing )
instead of ' I get:  â\200\231
2. All non-english characters get garbled, on all pages. These are
characters like ç, ö, etc.

With these two seemingly separate errors, I can't figure out whether this is
an lpr or enscript error.

* The file being sent through lpr is a simple text file.
* /etc/printcap entry for default printer is:
   lp|hp2100|HP 2100TN:\
   :rm=192.168.1.9:rp=raw:\
   :if=/usr/local/libexec/filters/psif:\
   :lf=/var/log/lpd-filter-errs:\
   :sd=/var/spool/lpd/hp2100:\
   :mx=0:sh:
* /var/log/lpd-filter-errs shows: [ 4 pages * 1 copy ] left in -  \  59
lines were wrapped  \  7 non-printable characters
* filetrs/psif is also very basic:
#!/bin/sh
IFS= read -r first_line
first_two_chars=`expr $first_line : '\(..\)'`
case $first_two_chars in
%!)
# %! : PostScript job, print it.
echo $first_line  cat  exit 0
exit 2
;;
*)
# otherwise, format with enscript
( echo $first_line; cat ) | /usr/local/bin/enscript -o -  exit 0
exit 2
;;
esac




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/printing-text-file-with-LPD-non-printable-characters-tp5954561.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

printing text file with LPD - non-printable characters

2014-10-05 Thread Beeblebrox

@Matthias:
 I moved the thread by setting Reply-To: to the normal
 freebsd-question@ list;
I'm using the nabble interface, so if the move does not work.. (I've never 
tried with moved thread before).

 First of all check, what encoding has your text file, UTF-8 or ISO or
$ file print.txt   UTF-8 Unicode text, with very long lines
 
 Then run the file through the filter
Thanks for that idea - helped narrow down the problem to enscript:
$ enscript mytext.txt -o filter.txt
[ 4 pages * 1 copy ] left in ens.txt
59 lines were wrapped
7 non-printable characters
Resulting file has same encoding errors as hard copy.

* I should also mention that I tried this from both Desktop and from tty* with 
same results.
* Will any environment settings affect this? The only relevant entry is: 
LANG=en_US.UTF-8

Regards.
-- 
FreeBSD_amd64_11-Current_RadeonKMS




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/printing-text-file-with-LPD-non-printable-characters-tp5954561p5954593.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: shmget (No space left on device) issue with firefox

2014-09-25 Thread Beeblebrox

All 3 mozilla-based ports that I have installed (Firefox, Seamonkey,
Thunderbird) crash immediately.

* Does anyone else on 11 have this problem or is it just me?
* I had been merging the linux-c6 ports into my tree for some time (now part
of the official tree) - could this have any relation to the problem (due to
flash-player)? This does not explain Thunderbird however.

Regards.



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/shmget-No-space-left-on-device-issue-with-firefox-tp5938162p5951793.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

zpool frag

2014-09-21 Thread Beeblebrox

FRAG means fragmentation, right? Zpool fragmentation? That's news to me. If
this is real how do I fix it?

NAME  SIZE  ALLOC   FREE   FRAG  EXPANDSZCAP  DEDUP  HEALTH  ALTROOT
pool1  75.5G  53.7G  21.8G60% -71%  1.00x  ONLINE  -
pool2  48.8G  26.2G  22.6G68% -53%  1.00x  ONLINE  -
pool3   204G   177G  27.0G53% -86%  1.11x  ONLINE  -

Regards.



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/zpool-frag-tp5950788.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

shmget (No space left on device) issue with firefox

2014-08-14 Thread Beeblebrox

I have been having difficulty getting firefox to work, so I built it with
DEBUG and this error shows up when starting with $ firefox -safe-mode =
shmget failed: error 28 (No space left on device)

What Shared Memory setting do I need to change so as to get rid of this
error? Alternatively, is this a mozilla bug? shmall looks sufficiently large
to me, and setting it to unlimited seems a bit risky.

My Shared Memory settings ATM on 4G physical RAM:
$  ipcs -M
shmmax:536870912
shmmin:1
shmmni:  192
shmseg:  128
shmall:   131072

MEMORY INFORMATION:
mem_wire:1543798784 (   1472MB) [ 39%]
mem_active:  +451334144 (430MB) [ 11%]
mem_inactive:+   1510998016 (   1441MB) [ 38%]
mem_cache:   +0 (  0MB) [  0%]
mem_free:+378961920 (361MB) [  9%]
mem_gap_vm:  +  1544192 (  1MB) [  0%]
--  --- --
mem_all: =   3886637056 (   3706MB) [100%]
mem_gap_sys: +123482112 (117MB)
--  ---
mem_phys:=   4010119168 (   3824MB)
mem_gap_hw:  +284848128 (271MB)
--  ---
mem_hw:  =   4294967296 (   4096MB)






-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/shmget-No-space-left-on-device-issue-with-firefox-tp5938162.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Several minor annoyances on Current

2014-07-31 Thread Beeblebrox

 hm, I have similar experience with 10-stable see
 http://lists.freebsd.org/pipermail/freebsd-questions/2014-July/259067.html

Thankfully, my boot time is not so severe. I have no ideas to help however.

* preventing coredump files:
setting in ~/.cshrc below does not work. What is the correct syntax?
ulimit -c 0
setenv  ulimit -c 0

* What is the error below? Could this output hold clues to finding deeper 
errors? This occurred during an install requiring opengl, but could Radeon-KMS 
be a contributing cause?

Not running in a graphics capable console, and unable to find one.
svgalib: ark: Unknown chiptype 29.
Not running in a graphics capable console, and unable to find one.
Not running in a graphics capable console, and unable to find one.
*** Error code 1





-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Several-minor-annoyances-on-Current-tp5931653p5933755.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

zdb: specify object_id for dataset of the zpool name

2014-07-29 Thread Beeblebrox

If I do zdb -dd mypool, It shows me the data from entire pool and all its
datasets, when in fact I only want the list from the mypool dataset. The
dataset ID is 21, so is there any syntax like:
# zdb -dd ID=21
I'm not trying to filter the output - I'm trying to dozdb -d mypool
object_id , which does not work when using the zpool name because zdb
looks at the pool-level data and returns error (no such object).



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/zdb-specify-object-id-for-dataset-of-the-zpool-name-tp5933179.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Several minor annoyances on Current

2014-07-26 Thread Beeblebrox

@ Ian:
I added your code and rebuilt the kernel.
/boot/loader.conf also has vfs.nfs.bootp_disable=YES
Previously described problem persists.

SEPARATE KBD_KEYMAP ISSUE:
The keymap for keyboard fails to be set from rc.conf with
keymap=fr.iso.kbd
Boot message shows this but there is no record of the message in log 
files/dmesg: Configuring syscons: keymapkbdcontrol: keymap file fr.iso.kbd 
not found: No such file or directory
Keymap gets set when I change rc.conf entry to: 
keymap=/usr/share/syscons/keymaps/fr.iso.kbd





-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Several-minor-annoyances-on-Current-tp5931653p5931938.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Several minor annoyances on Current

Hello. Several questions for 11-Current:

* I keep getting appname.core (gedit.core, midori.core, etc) files being
created either in /home/myuser or in the folder I run the command in on
terminal emulator (for example if I'm in ~/mydocs on terminal and run $
gedit filename, that folder gets a gedit.core file). Any way to stop this?

* I noticed the system now does a dhcp lookup during boot, while in the past
it did not do so (I have static IP defined in rc.conf). Any reason for this
change, and how can I disable it (already have dhclient_enable=NO in
rc.conf)

* Are there any tweaks (sysctl or such) for fastest possible shutdown for
poweroff?

* I have a kernel with all witness/debug code disabled, and the zfs root is
on a Sata3-SSD. The boot process seems a little slow to me and I'm curious
as to possible reasons. Other than disabling debug, what else can I do to
speed-up boot process (CPU: AMD Phenom II X4 B60 3415.38-MHz K8-class)

Thanks and Regards.



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Several-minor-annoyances-on-Current-tp5931653.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Several minor annoyances on Current

 Damian Weber wrote:
is there 
ifconfig_em0=DHCP 
or anything like that in your rc.conf?

No, network related rc.conf entries:
network_interfaces=lo0 re0 re1
ifconfig_lo0=inet 127.0.0.1/24
ifconfig_re0=inet 192.168.1.10/24
ifconfig_re1=inet 192.168.2.1/24
gateway_enable=YES
defaultrouter=192.168.1.1
dhclient_enable=NO

Thanks  regards.



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Several-minor-annoyances-on-Current-tp5931653p5931665.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Several minor annoyances on Current

Kurt Jaeger wrote:

 Can you check whether one of your ethernet-ports has a double life
 as IPMI port and that one sends out the DHCP ?

No such setup. This is my workstation, with wake-on-lan and pxe-boot
disabled in bios.
Checking boot messages provides a little more insight - Its not one but
*both* NIC's that look for DHCP. Also, this is before root gets mounted, so
what's in rc.conf is irrelevant:

Sending DHCP Discover packet from interface re0 (mac#)
Sending DHCP Discover packet from interface re1 (mac#)
Received DHCP Offer packet on re0 from 192.168.1.1 (accepted)
Received DHCP Offer packet on re0 from 192.168.1.1 (ignored)
Received DHCP Offer packet on re0 from 192.168.1.1 (ignored)
Sending DHCP Request packet from interface re0 (mac#)
Received DHCP Ack packet on re0 from 192.168.1.1 (accepted)
DHCP timeout for interface re1
re0 at 192.168.1.11 server 192.168.1.1
subnet mask 255.255.255.0 router 192.168.1.1
Adjusted interface re0
Shutdown interface re1
Trying to mount root from zfs:bsd []...

I compile and use the same kernel for both host and pxe-booted diskless
clients. So my kernel config file has
options NFSCL   # Network Filesystem Client
options NFS_ROOT# NFS usable as /, requires NFSCL
options BOOTP   # Needed for non-btx PXE
options BOOTP_NFSROOT   # Needed for non-btx PXE
It's probably what's causing this behavior. Kernel must receive IP before it
can try and mount an NFS volume as root. However, I would have assumed that
the vfs.root.mountfrom= setting in loader.conf would be read before such
attempt...



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Several-minor-annoyances-on-Current-tp5931653p5931678.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Several minor annoyances on Current

 ... in retrospect I can think of
 several good reasons to turn off bootp on a per-boot basis.  The
 attached patch provides a knob for that, I'll commit it if there are
 no objections.

Thanks - a knob in /boot/loader.conf as
vfs.nfs.bootp_disable=YES
should do nicely.

Regards.




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Several-minor-annoyances-on-Current-tp5931653p5931753.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Several minor annoyances on Current

Hi

 This seems like a job for ulimit.
Damien pointed that out as: ulimit -c 0

 Though, I would be more curious about why your applications are
 crashing so as to generate core files in the first place.

Well, this MAJOR annoyance lies somewhere between Radeon-KMS and gnome3's 
graphics/cairo. This started some 3 months back and I can only get some level 
of normalcy when I build cairo using with_debug=1. Very strange. Also, a 
number of apps just flat-out refuse to start; most notably mozilla's firefox  
seamonkey. Monsieur Pédron is aware of the problem, although as stated it's 
been over 3 months.

While I'm on a roll :P
One major peeve is that installed apps fail to create an icon in the desktop 
menu structure. I know that
a) maintainer must set DESKTOP_ENTRIES in the Makefile OR
b) users can add appname.desktop in /usr/local/share/applications/
but as a dreamer, I know there has to be a better solution other than badgering 
maintainers or slogging through the task of adding menu shortcut items?




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Several-minor-annoyances-on-Current-tp5931653p5931761.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Several minor annoyances on Current

Hi
 I use this in /etc/sysctl.conf:
 kern.corefile=/tmp/cores/%N.core

In rc.conf I have
clear_tmp_enable=YES
I would have used tmpfs for /tmp but my zpool/tmp is on an SSD which gives 
about the same result as far as /tmp is concerned.
The ulimit setting seems to have solved it.




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Several-minor-annoyances-on-Current-tp5931653p5931773.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Previously working PXE setup now fails

2014-06-24 Thread Beeblebrox

Hi and thanks for your input. If I may, I have several more Q's regarding
this issue:

 As I think I've mentioned before, a NFSv4 root fs won't work, so don't
 bother trying...
Q1: I did not realise that. I took out the V4:  in exports. However, is it
possible to have a mixed-mode, something like /data/amd64 as V3 but /home as
V4?

Q2: I now get to the BTX loader, wireshark shows correct mount call
192.168.2.3, 192.168.2.1, MOUNT, V3 MNT Call (Reply In 14072) /data/amd64.
Unfortunately, I get a complete black screen when I hit enter from BTX (it
looks like a lock-up) and wireshark shows no traffic for the problem.

To get to this point, I re-anabled some of what I had taken out before, and
I now forget which config options are necessary at this point. What I have:
(always had this) fstab: 192.168.2.1:/data/amd64  /  nfs  ro 0 0

boot/loader.conf:
boot.nfsroot.server=192.168.2.1
boot.nfsroot.path=/data/amd64
##_re-enabled_##
vfs.root.mountfrom=nfs:192.168.2.1:/data/amd64
vfs.root.mountfrom=nfs
boot.nfsroot.options=nolockd
vfs.root.mountfrom.options=ro

re-enabled in dhcpd.conf
option root-path 192.168.2.1:/data/amd64; 

I can't figure out what needs to be modified and what options can be
removed?

Thanks for your help.



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Previously-working-PXE-setup-now-fails-tp5919662p5923355.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Previously working PXE setup now fails

2014-06-23 Thread Beeblebrox

 see if you can run wireshark on your NFS server that is being mounted.
 That should narrow down the RPC error.

It took a while to get around to this, but the problem looks like NFS
v3 - v4 conflict. Wireshark shows these errors:
Program Version: 3 \ V3 Procedure: MNT (1) \Status: ERR_ACCESS (13)

But NFS is started as v4. /etc/exports (not sure if correct syntax):
V4:  / -network 192.168.2.0/26
/data/amd64 -ro -network 192.168.2.0/26 # NFS root
/usr/local  -ro -maproot=0 -network 192.168.2.0/26
/home   -network 192.168.2.0/26

The PXE structure (dhcp  tftp) are started as a jail with the jail
root folder as the NFS export root (/data/amd64). The jail and NFS
services are not started with boot but with separate script.

/etc/rc.conf has:
rpcbind_flags=-h 192.168.2.1
mountd_flags=-r -n -l -h 192.168.2.1
nfsd_flags=-u -t -n 4 -h 192.168.2.1
nfsv4_only=YES
nfsv4_server_enable=YES

pxe_start_script.sh:
jail -c pxe
service rpcbind onestart
service mountd onestart
service nfsd onestart
service nfsuserd onestart
# disabled_not_needed? rpc_lockd_enable=YES  rpc_statd_enable=

I should probablymove the rc.conf flags into my pxe_start_script.sh,
but not sure how to pass service start flags in an sh script.

Regards.

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

Previously working PXE setup now fails

2014-06-10 Thread Beeblebrox

I had a perfectly working PXE-booting environment, but now it fails at kernel
boot stage.

Client starts to boot, and var/log/xfer shows the pxeboot file being
transferred from server:
  in.tftpd[34792]: RRQ from 192.168.2.3 filename pxeboot
  tftpd[5013]: Filename: 'pxeboot'
  tftpd[5015]: Mode: 'octet'
  tftpd[5015]: 192.168.2.3: read request for //pxeboot: success

Then BTX starts to boot the kernel but fails with:
  pxe_open: server addr: 192.168.2.1
  pxe_open: server path: /
  pxe_open: gateway ip: 192.168.2.1
  NFS MOUNT RPC error: 72
  /
  can't load 'kernel'

Then drops to BTX's rescue command prompt.
* NFS path is visible in showmount -e and I have disabled NFS_V4 to debug
the problem.
* The BTX cli gives failed RPC struct is bad message to ls command.
* rpcbind complains cannot get information for tcp6  udp6. My kernel has
IPV6 disabled and etc/rc.conf has {ipv6_activate_all_interfaces=NO \
ip6addrctl_enable=NO}
* etc/rc.conf has these as well and I tried the problem with NFS_V3 (disable
V4) but got same result:
rpcbind_flags=-h 192.168.2.1
mountd_flags=-r -n -o -l -h 192.168.2.1
nfsd_flags=-u -t -n 4 -h 192.168.2.1
#nfsv4_only=YES
#nfsv4_server_enable=YES
* The only other log entry I can find is:
inetd[4949]: madvise() failed: Operation not permitted
inetd[5012]: setpriority 'root' (daemon): Permission denied
inetd[5014]: setpriority 'root' (daemon): Permission denied

Any suggestions on what else I can try to debug this thing?



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/Previously-working-PXE-setup-now-fails-tp5919662.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

jail sockstat shows gdnc, gdomap, casperd as enabled

Some (not all) of my jails show gdnc, gdomap  casperd services with sockstat
listing. The jails that show these services have /usr/local mounted as ro to
jailname/usr/local.

root gdnc   1433  5  stream
/tmp/GNUstepSecure0/NSMessagePort/ports/1433.0
nobody   gdomap 1378  3  udp4   192.168.2.50:538  *:*
nobody   gdomap 1378  4  tcp4   192.168.2.50:538  *:*
root casperd1149  3  dgram  - /var/run/logpriv
root casperd1149  4  stream - ??
root casperd1149  6  stream /var/run/casper
root casperd1148  5  stream - ??

Why are these services running? Can I safely disable them (and how)?

Thanks  Regards.



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/jail-sockstat-shows-gdnc-gdomap-casperd-as-enabled-tp5917302.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: jail sockstat shows gdnc, gdomap, casperd as enabled

Hi Trond,

These two are related to GNUstep. If your jails don't run GNUstep, why
 is GNUstep installed in the first place?


I know that they are related to GNUstep (although I have no idea what
GNUstep actually does other than act as a messaging system probably like
dbus). Anyway, I don't understand how  why they start up and that's
exactly my question. The only insight I can provide, is that /usr/local is
null_mounted on to jail/usr/local, but that should not really have this
effect.


 casperd is part of capsicum. You should probably keep this one.

I figured as much re capsicum. So the question becomes should all jails be
running capsicum in this case?

Regards.




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/jail-sockstat-shows-gdnc-gdomap-casperd-as-enabled-tp5917302p5917311.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: jail sockstat shows gdnc, gdomap, casperd as enabled

 I'd strongly recommend firewalling (Both gdomap and gdnc) off from the
outside world.

I want to completely disable them, not just for the above, but also because
they unnecessarily consume memory. It adds up when you have 5-6 jails
running.

@Trond: Point taken for casperd - I'll keep it in my jails.

The /usr/local mount_nullfs to the jail is what seems to cause this. I
modified one of the jail's fstab and disabled the service it was running in
rc.conf. The differences in start-up are obvious. 

A. /usr/local mount disabled
jail -c http
http: created
Creating and/or trimming log files.
ln: /dev/log: Operation not permitted
Starting syslogd.
ELF ldconfig path: /lib /usr/lib /usr/lib/compat
32-bit compatibility ldconfig path: /usr/lib32
Starting casperd.
Clearing /tmp.
Starting cron.

B. When mounting /usr/local jailname/usr/local nullfs ro 0 0
jail -c http
http: created
ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib
/usr/local/GNUstep/Local/Library/Libraries
/usr/local/GNUstep/System/Library/Libraries /usr/local/lib/R/lib
/usr/local/lib/ardour2 /usr/local/lib/ardour2/surfaces /usr/local/lib/event2
/usr/local/lib/ffmpeg0 /usr/local/lib/gcc47 /usr/local/lib/gegl-0.2
/usr/local/lib/gnutls3 /usr/local/lib/graphviz /usr/local/lib/httrack
/usr/local/lib/libxul /usr/local/lib/mysql /usr/local/lib/nss
/usr/local/lib/portaudio2
/usr/local/lib/pth /usr/local/lib/qt4 /usr/local/lib/virtualbox
/usr/local/llvm33/lib
32-bit compatibility ldconfig path: /usr/lib32 /usr/local/lib32
/usr/local/lib32/wine
Creating and/or trimming log files.
ln: /dev/log: Operation not permitted
Starting syslogd.
Starting casperd.
Clearing /tmp.
/usr/local/etc/rc.d/gkrellmd: set_rcvar: not found
/etc/rc: WARNING: run_rc_command: cannot run /usr/local/sbin/gkrellmd
/etc/rc: WARNING: $pfstatd_enable is not set properly - see rc.conf(5).
Starting cron.
Local package initialization: GNUstep/usr/local/etc/rc.d/jail.sh:
/usr/local/sbin/jail_ps: not
found
 jails.

C. Shutting it down
jail -r http
Shutting down local packages:/usr/local/etc/rc.d/jail.sh:
/usr/local/sbin/jail_ps: not found
 GNUstep.
Stopping cron.
Waiting for PIDS: 1704.
/etc/rc.shutdown: WARNING: $pfstatd_enable is not set properly - see
rc.conf(5).
/usr/local/etc/rc.d/gkrellmd: set_rcvar: not found
Stopping casperd.
Waiting for PIDS: 1581.
Terminated
http: removed




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/jail-sockstat-shows-gdnc-gdomap-casperd-as-enabled-tp5917302p5917336.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: jail sockstat shows gdnc, gdomap, casperd as enabled