Re: Oddball error from "batch"

2019-02-10 Thread Karl Denninger
On 2/10/2019 16:01, Karl Denninger wrote: > Note -- working fine on 11.1 and 11.2, upgraded machine to 12.0-STABLE > and everything is ok that I'm aware of *except*. > > # batch > who > df > ^D > > Job 170 will be executed using /bin/sh > > Then the time comes and... no output is emailed to

Oddball error from "batch"

2019-02-10 Thread Karl Denninger
Note -- working fine on 11.1 and 11.2, upgraded machine to 12.0-STABLE and everything is ok that I'm aware of *except*. # batch who df ^D Job 170 will be executed using /bin/sh Then the time comes and... no output is emailed to me. In the cron log file I find: Feb 10 16:00:00 NewFS

Repeated kernel panic on 11.2-RELEASE-p7

2019-02-10 Thread Jurij Kovačič via freebsd-stable
Dear list, After some time, I have again experienced a kernel panic on a (physical) server, running Freebsd 11.2-RELEASE-p7 with custom/debug kernel, ZFS root. Fatal trap 9: general protection fault while in kernel mode cpuid = 2; apic id = 02 instruction pointer= 0x20:0x82299013

Problem reports for sta...@freebsd.org that need special attention

2019-02-10 Thread bugzilla-noreply
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

Re: Geli prompts on gptzfsboot (Was:: Serious ZFS Bootcode Problem (GPT NON-UEFI -- RESOLVED)

2019-02-10 Thread Karl Denninger
On 2/10/2019 12:40, Ian Lepore wrote: > On Sun, 2019-02-10 at 12:35 -0600, Karl Denninger wrote: >> On 2/10/2019 12:01, Ian Lepore wrote: >>> On Sun, 2019-02-10 at 11:54 -0600, Karl Denninger wrote: On 2/10/2019 11:50, Ian Lepore wrote: > On Sun, 2019-02-10 at 11:37 -0600, Karl Denninger

Re: Geli prompts on gptzfsboot (Was:: Serious ZFS Bootcode Problem (GPT NON-UEFI -- RESOLVED)

2019-02-10 Thread Ian Lepore
On Sun, 2019-02-10 at 12:35 -0600, Karl Denninger wrote: > On 2/10/2019 12:01, Ian Lepore wrote: > > On Sun, 2019-02-10 at 11:54 -0600, Karl Denninger wrote: > > > On 2/10/2019 11:50, Ian Lepore wrote: > > > > On Sun, 2019-02-10 at 11:37 -0600, Karl Denninger wrote: > > > > > > > > > [...] > > >

Re: Geli prompts on gptzfsboot (Was:: Serious ZFS Bootcode Problem (GPT NON-UEFI -- RESOLVED)

2019-02-10 Thread Karl Denninger
On 2/10/2019 12:01, Ian Lepore wrote: > On Sun, 2019-02-10 at 11:54 -0600, Karl Denninger wrote: >> On 2/10/2019 11:50, Ian Lepore wrote: >>> On Sun, 2019-02-10 at 11:37 -0600, Karl Denninger wrote: >>> [...] BTW am I correct that gptzfsboot did *not* get the ability to read

Re: Fwd: Serious ZFS Bootcode Problem (GPT NON-UEFI)

2019-02-10 Thread Ian Lepore
On Sun, 2019-02-10 at 11:37 -0600, Karl Denninger wrote: > On 2/10/2019 09:28, Allan Jude wrote: > > Are you sure it is non-UEFI? As the instructions you followed, > > overwriting da0p1 with gptzfsboot, will make quite a mess if that > > happens to be the EFI system partition, rather than the

Re: Fwd: Serious ZFS Bootcode Problem (GPT NON-UEFI)

2019-02-10 Thread Ian Lepore
On Sun, 2019-02-10 at 11:54 -0600, Karl Denninger wrote: > On 2/10/2019 11:50, Ian Lepore wrote: > > On Sun, 2019-02-10 at 11:37 -0600, Karl Denninger wrote: > > > On 2/10/2019 09:28, Allan Jude wrote: > > > > Are you sure it is non-UEFI? As the instructions you followed, > > > > overwriting da0p1

Re: Fwd: Serious ZFS Bootcode Problem (GPT NON-UEFI)

2019-02-10 Thread Karl Denninger
On 2/10/2019 11:50, Ian Lepore wrote: > On Sun, 2019-02-10 at 11:37 -0600, Karl Denninger wrote: >> On 2/10/2019 09:28, Allan Jude wrote: >>> Are you sure it is non-UEFI? As the instructions you followed, >>> overwriting da0p1 with gptzfsboot, will make quite a mess if that >>> happens to be the

Re: Fwd: Serious ZFS Bootcode Problem (GPT NON-UEFI)

2019-02-10 Thread Karl Denninger
On 2/10/2019 09:28, Allan Jude wrote: > Are you sure it is non-UEFI? As the instructions you followed, > overwriting da0p1 with gptzfsboot, will make quite a mess if that > happens to be the EFI system partition, rather than the freebsd-boot > partition. Absolutely certain.  The system board in

amd64, run-time linker and 32bit

2019-02-10 Thread Eugene Grosbein
Hi! Why our 32-bit run-time linker looks for shared libraries in the /usr/local/lib despite of its absence in /var/run/ld-elf32.so.hints while 32-bit binary is started under FreeBSD 11.2-STABLE/amd64 ? If it finds 64-bit version of library in /usr/local/lib, it fails immediately and does not