Re: I'm upset about FreeBSD

2016-10-19 Thread Kevin Oberman 
On Wed, Oct 19, 2016 at 3:39 PM, Warner Losh  wrote:

> On Wed, Oct 19, 2016 at 12:21 PM, Rostislav Krasny 
> wrote:
> > On Tue, Oct 18, 2016 at 21:57:29 +1100, Ian Smith 
> wrote:
> >>
> >> If FreeBSD GPT images (and Kindle readers) can trigger this, so could a
> >> theoretically unlimited combination of data on block 2 of USB media;
> >> modifying FreeBSD to fix a Windows bug should be out of the question.
> >
> > Not modifying FreeBSD and not fixing Windows bug but modifying the
> > FreeBSD installation media and working around the Windows bug to let
> > people install FreeBSD without disappointing at very beginning. Why
> > GPT is used in the memstick images at all? Why they can't be MBR
> > based? I think they can.
>
> Can't boot UEFI off of MBR disks on all BIOSes.
>
> Warner
>

I'll go one farther. You can't boot many new PCs with traditional MBR
disks. And. please don't  confuse GPT with UEFI. I have yet to find an
amd64 computer that has a problem with a GPT format with MBR. Due to broken
BIOS, my 5-year old ThinkPad won't boot UEFI, but it has no problem with
MBR, whether GPT formatted or not. As far as I know, the 11.0 memstick
images are still MBR, just on a GPT structured disk, not UEFI. (Let me know
if I am mistaken on this.)

I do accept that some early amd64 systems and, perhaps, many i386 systems
may have problems with GPT, but GPT was designed to be compatible with
traditional disk formats and, while they may have problems, they really
should work for single partition disks. And I understand that it is
frustrating if you hit one of these cases where it fails.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: I'm upset about FreeBSD

2016-10-19 Thread Warner Losh 
On Wed, Oct 19, 2016 at 12:21 PM, Rostislav Krasny  wrote:
> On Tue, Oct 18, 2016 at 21:57:29 +1100, Ian Smith  
> wrote:
>>
>> If FreeBSD GPT images (and Kindle readers) can trigger this, so could a
>> theoretically unlimited combination of data on block 2 of USB media;
>> modifying FreeBSD to fix a Windows bug should be out of the question.
>
> Not modifying FreeBSD and not fixing Windows bug but modifying the
> FreeBSD installation media and working around the Windows bug to let
> people install FreeBSD without disappointing at very beginning. Why
> GPT is used in the memstick images at all? Why they can't be MBR
> based? I think they can.

Can't boot UEFI off of MBR disks on all BIOSes.

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

Jenkins build is still unstable: FreeBSD_stable_10 #434

2016-10-19 Thread jenkins-admin 
https://jenkins.FreeBSD.org/job/FreeBSD_stable_10/434/
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.0 Install Question

2016-10-19 Thread Gary Palmer 
On Wed, Oct 19, 2016 at 01:55:23PM -0400, Kevin P. Neal wrote:
> On Wed, Oct 19, 2016 at 10:08:04AM +0100, Matthew Seaman wrote:
> > On 2016/10/19 09:55, Matt Smith wrote:
> > > On Oct 19 10:38, Miroslav Lachman wrote:
> > >> Jonathan Haack wrote on 2016/10/19 10:09:
> > >>> Awe geez ... pkg won't work ... says "shared object "libssl.so.7" not
> > >>> found, required by "pkg"
> > >>
> > >> Do not panic, just run pkg-static to upgrade pkg it-self
> > >>
> > >> /usr/local/sbin/pkg-static install -f pkg
> > >>
> > > 
> > > I think that these instructions should be in the announcement release
> > > notes as this question comes up a lot. The notes just say something like
> > > "upgrade all your packages". Most people will then just try and run pkg
> > > upgrade and get that error without knowing how to solve it. It's not
> > > intuitive unless you have come across this before.
> > 
> > pkg(8) does have a built-in warning when it detects an OS major version
> > upgrade, which is to do a forced upgrade of pkg(8) so it matches the ABI
> > versions of system shlibs.  Did that warning appear in this case?
> 
> Loading of shared libraries generally happens before main() is entered.
> It follows that pkg wouldn't have a chance to do anything useful before
> dying if a library is missing.

Hi,

I don't think this is strictly true

On one of my systems at least (10.x), the main pkg binary is in
/usr/sbin which is a shim which either offers to install a full
pkg binary or calls the full pkg binary with whatever arguments you
passed it.  The main pkg binary lives in /usr/local/sbin/pkg.

It seems it should be possible to add some kind of check to the
shim to "do the right thing" and offer to use pkg-static to
upgrade the main pkg binary if the dynamically linked one is
broken.  Or maybe it should default to calling pkg-static instead
of pkg, which would prevent the problem in the first place.

Of course this assumes the user has /usr/sbin before /usr/local/sbin
on their path, but I suspect that is true in most cases

Regards,

Gary

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

Re: I'm upset about FreeBSD

2016-10-19 Thread Rostislav Krasny 
On Tue, Oct 18, 2016 at 21:57:29 +1100, Ian Smith  wrote:
>
> If FreeBSD GPT images (and Kindle readers) can trigger this, so could a
> theoretically unlimited combination of data on block 2 of USB media;
> modifying FreeBSD to fix a Windows bug should be out of the question.

Not modifying FreeBSD and not fixing Windows bug but modifying the
FreeBSD installation media and working around the Windows bug to let
people install FreeBSD without disappointing at very beginning. Why
GPT is used in the memstick images at all? Why they can't be MBR
based? I think they can.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

tcsh is not handled correctly UTF-8 in arguments

2016-10-19 Thread Slawa Olhovchenkov 
tcsh called by sshd for invocation of scp: `tcsh -c scp -f Расписание.pdf`
At this time no any LC_* is set.
tcsh read .cshrc and set LC_CTYPE=ru_RU.UTF-8 LC_COLLATE=ru_RU.UTF-8.
After this invocation of scp will be incorrect:

7ab0  20 2d 66 20 c3 90 c2 a0  c3 90 c2 b0 c3 91 c2 81  | -f |
7ac0  c3 90 c2 bf c3 90 c2 b8  c3 91 c2 81 c3 90 c2 b0  ||
7ad0  c3 90 c2 bd c3 90 c2 b8  c3 90 c2 b5 5f c3 90 c2  |_...|
7ae0  a2 c3 90 c2 97 c3 90 c2  98 2e 70 64 66 0a|..pdf.  |

Correct invocation must be:

   20 2d 66 20  | -f |
0010  d0 a0 d0 b0 d1 81 d0 bf  d0 b8 d1 81 d0 b0 d0 bd  ||
0020  d0 b8 d0 b5 5f d0 a2 d0  97 d0 98 2e 70 64 66 0a  |_...pdf.|

`d0` =>  `c3 90`
`a0` =>  `c2 a0`

I.e. every byte re-encoded to utf-8: `d0` =>  `c3 90`

As result imposible to access files w/ non-ascii names.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Jenkins build is still unstable: FreeBSD_stable_10 #433

2016-10-19 Thread jenkins-admin 
https://jenkins.FreeBSD.org/job/FreeBSD_stable_10/433/
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: LOR in mpr(4)

2016-10-19 Thread Pete Wright 



On 10/19/16 8:10 AM, geoffroy desvernay wrote:

On 11/17/2015 21:43, Pete Wright wrote:



On 11/12/15 09:44, Pete Wright wrote:

Hi All,
Just wanted a sanity check before filing a PR.  I am running r290688 and
am seeing a LOR being triggered in the mpr(4) device:

$ uname -ar
FreeBSD srd0013 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r290688: Wed Nov 11
21:28:26 PST 2015 root@srd0013:/usr/obj/usr/src/sys/GENERIC  amd64


lock order reversal:
 1st 0xf8000d26bc60 CAM device lock (CAM device lock) @
/usr/src/sys/cam/cam_xpt.c:784
 2nd 0xfe00012811c0 MPR lock (MPR lock) @
/usr/src/sys/cam/cam_xpt.c:2620
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
0xfe04608ee890
witness_checkorder() at witness_checkorder+0xe79/frame 0xfe04608ee910
__mtx_lock_flags() at __mtx_lock_flags+0xa4/frame 0xfe04608ee960
xpt_action_default() at xpt_action_default+0xb6c/frame 0xfe04608ee9b0
scsi_scan_bus() at scsi_scan_bus+0x1d5/frame 0xfe04608eea20
xpt_scanner_thread() at xpt_scanner_thread+0x15c/frame 0xfe04608eea70
fork_exit() at fork_exit+0x84/frame 0xfe04608eeab0
fork_trampoline() at fork_trampoline+0xe/frame 0xfe04608eeab0
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---



FWIW I filed the following PR as I can still reproduce this on boot:

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

cheers,
-pete


Hi all,

Sorry for cross-posting, let me know where this should go please, I
didn't figured it out :(

On 11-RELEASE-p1 here (but replying on current@ where I found something
around mpr(4))

Not sure if it's related, but on a fresh new machine with Avago SAS3008
and a 24 disks enclosure (single attached).

I see a bunch of:

mpr0: Found device <401,End Device> <12.0Gbps> handle<0x001b>
enclosureHandle<0x0002> slot 8
(da0:mpr0:0:8:0): UNMAPPED
(da0:mpr0:0:8:0): CAM status: SCSI Status Error
(da0:mpr0:0:8:0): SCSI status: Check Condition
(da0:mpr0:0:8:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command
operation code)
(da0:mpr0:0:8:0): Error 22, Unretryable error
10:0): UNMAPPED
(da0:mpr0:0:8:0): READ(10). CDB: 28 00 e8 e0 88 71 00 00 04 00
(da0:mpr0:0:8:0): CAM status: SCSI Status Error
(da0:mpr0:0:8:0): SCSI status: Check Condition
(da0:mpr0:0:8:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command
operation code)
(da0:mpr0:0:8:0): Error 22, Unretryable error
ses0: da0: Element descriptor: 'Drive Slot 0'
ses0: da0: SAS Device Slot Element: 2 Phys at Slot 0
ses0:  phy 0: SAS device type 1 id 0
ses0:  phy 0: protocols: Initiator( None ) Target( SSP )
ses0:  phy 0: parent 520474729974b57f addr 5000c50097ce8215
ses0:  phy 1: SAS device type 1 id 1
ses0:  phy 1: protocols: Initiator( None ) Target( SSP )
ses0:  phy 1: parent 520474729974b5ff addr 5000c50097ce8216

(more complete dmesg.boot here: http://dgeo.perso.ec-m.fr/dmesg.boot )



the issue you are seeing is most likely not related to the LOR from the 
original email and PR I filed.  This looks like a media error with the 
disk device on your RAID controller.  A quick google search turn's up 
quite a few threads on this - ranging from bad RAID/JBOD controllers to 
out of date firmware.


Cheers,
-pete



--
Pete Wright
p...@nomadlogic.org
nomadlogicLA
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: LOR in mpr(4)

2016-10-19 Thread geoffroy desvernay 
On 11/17/2015 21:43, Pete Wright wrote:
> 
> 
> On 11/12/15 09:44, Pete Wright wrote:
>> Hi All,
>> Just wanted a sanity check before filing a PR.  I am running r290688 and
>> am seeing a LOR being triggered in the mpr(4) device:
>>
>> $ uname -ar
>> FreeBSD srd0013 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r290688: Wed Nov 11
>> 21:28:26 PST 2015 root@srd0013:/usr/obj/usr/src/sys/GENERIC  amd64
>>
>> 
>> lock order reversal:
>>  1st 0xf8000d26bc60 CAM device lock (CAM device lock) @
>> /usr/src/sys/cam/cam_xpt.c:784
>>  2nd 0xfe00012811c0 MPR lock (MPR lock) @
>> /usr/src/sys/cam/cam_xpt.c:2620
>> KDB: stack backtrace:
>> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
>> 0xfe04608ee890
>> witness_checkorder() at witness_checkorder+0xe79/frame 0xfe04608ee910
>> __mtx_lock_flags() at __mtx_lock_flags+0xa4/frame 0xfe04608ee960
>> xpt_action_default() at xpt_action_default+0xb6c/frame 0xfe04608ee9b0
>> scsi_scan_bus() at scsi_scan_bus+0x1d5/frame 0xfe04608eea20
>> xpt_scanner_thread() at xpt_scanner_thread+0x15c/frame 0xfe04608eea70
>> fork_exit() at fork_exit+0x84/frame 0xfe04608eeab0
>> fork_trampoline() at fork_trampoline+0xe/frame 0xfe04608eeab0
>> --- trap 0, rip = 0, rsp = 0, rbp = 0 ---
>> 
> 
> FWIW I filed the following PR as I can still reproduce this on boot:
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204614
> 
> cheers,
> -pete
> 
Hi all,

Sorry for cross-posting, let me know where this should go please, I
didn't figured it out :(

On 11-RELEASE-p1 here (but replying on current@ where I found something
around mpr(4))

Not sure if it's related, but on a fresh new machine with Avago SAS3008
and a 24 disks enclosure (single attached).

I see a bunch of:

mpr0: Found device <401,End Device> <12.0Gbps> handle<0x001b>
enclosureHandle<0x0002> slot 8
(da0:mpr0:0:8:0): UNMAPPED
(da0:mpr0:0:8:0): CAM status: SCSI Status Error
(da0:mpr0:0:8:0): SCSI status: Check Condition
(da0:mpr0:0:8:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command
operation code)
(da0:mpr0:0:8:0): Error 22, Unretryable error
10:0): UNMAPPED
(da0:mpr0:0:8:0): READ(10). CDB: 28 00 e8 e0 88 71 00 00 04 00
(da0:mpr0:0:8:0): CAM status: SCSI Status Error
(da0:mpr0:0:8:0): SCSI status: Check Condition
(da0:mpr0:0:8:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command
operation code)
(da0:mpr0:0:8:0): Error 22, Unretryable error
ses0: da0: Element descriptor: 'Drive Slot 0'
ses0: da0: SAS Device Slot Element: 2 Phys at Slot 0
ses0:  phy 0: SAS device type 1 id 0
ses0:  phy 0: protocols: Initiator( None ) Target( SSP )
ses0:  phy 0: parent 520474729974b57f addr 5000c50097ce8215
ses0:  phy 1: SAS device type 1 id 1
ses0:  phy 1: protocols: Initiator( None ) Target( SSP )
ses0:  phy 1: parent 520474729974b5ff addr 5000c50097ce8216

(more complete dmesg.boot here: http://dgeo.perso.ec-m.fr/dmesg.boot )

Later, no way to use these disks with zfs:
# zpool create tank da0
cannot create 'tank': invalid argument for this pool operation

I can dd if=/dev/zero of=/dev/da0 though not tested until disk is full…

Can this be related ? Must I open a pr ? How can I help debugging this ?

I'm not kernel/driver hacker, but I'd like to help this be figured out :)

Yours,
-- 
*geoffroy desvernay*
C.R.I - Administration systèmes et réseaux
Ecole Centrale de Marseille




signature.asc
Description: OpenPGP digital signature

Re: Building FreeBSD 11.0-stable on FreeBSD 10.1-stable fails

2016-10-19 Thread Warner Losh 
On Sun, Oct 16, 2016 at 12:18 PM, Dimitry Andric  wrote:
> On 16 Oct 2016, at 17:22, Warner Losh  wrote:
>>
>> On Sun, Oct 16, 2016 at 5:34 AM, Dimitry Andric  wrote:
>>> On 16 Oct 2016, at 12:20, Torfinn Ingolfsen  
>>> wrote:
 I am trying to build FreeBSD 11.0-stable on a machine which runs:
 tingo@kg-v7$ uname -a
 FreeBSD kg-v7.kg4.no 10.1-STABLE FreeBSD 10.1-STABLE #0 r278322: Fri Feb  
 6 21:36:01 CET 2015
 r...@kg-v7.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64

 I have emptied /usr/src and /usr/obj and fetched the latest stable/11 via 
 subversion:
 tingo@kg-v7$ egrep "^BRANCH|^REVISION" /usr/src/sys/conf/newvers.sh
 REVISION="11.0"
 BRANCH="STABLE"

 But building it (per the procedure in the handbook) fails at the 
 buildworld stage. Both 'make -j5 buildworld' and 'make buildworld' fails, 
 like this:

 c++: error: unable to execute command: Segmentation fault (core dumped)
> ...
>>> Please make sure your stable/10 is at least r286033.
>>
>> What's the issue this fixes?
>
> It fixes a possible crash in clang 3.4, which can occur if newer
> versions of llvm are compiled.  Unfortunately this fix only went in
> after 10.3-RELEASE.

I think you're confused. In prepping a patch, it looks like it went in
after 9.3-RELEASE on stable/9, but it went in between 10.2 and 10.3 on
stable/10. So 10.1R and 10.2R are busted, but 10.3R should work. I've
updated UPDATING to reflect this.

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

Re: 11.0 Install Question

2016-10-19 Thread Jonathan Haack 
Totally agree and since even though I had followed the instructions prior to 
that step, it had also fried my mate installation and GUI so ... I could not 
access control center or anything since it was gone ... I almost wiped and 
reverted back to 10.1 misinterpreting the outcome first ... once I ran that 
command, I reinstalled everything again and it fixed the mate package and 
machine was back to normal ...

Thanks again rocking now







Sincerely,

Coach Haack

DP Coordinator, Mandela International Magnet School
Board of Directors, First Serve NM
President, NMCTM

www.jonathanhaack.com

"It is better to have tried and failed than to have succeeded at doing 
nothing." 

Confidentiality Notice:  This email, including all attachments is for the sole 
use of the intended recipient or recipients and may contain confidential 
information.  Any unauthorized review, use, disclosure, or distribution, is 
prohibited unless specifically provided under the New Mexico Inspection of 
Public Records Act.  If you are not the intended recipient, please contact the 
sender and destroy all copies of this message.

> On Oct 19, 2016, at 2:55 AM, Matt Smith  wrote:
> 
>> On Oct 19 10:38, Miroslav Lachman wrote:
>> Jonathan Haack wrote on 2016/10/19 10:09:
>>> Awe geez ... pkg won't work ... says "shared object "libssl.so.7" not 
>>> found, required by "pkg"
>> 
>> Do not panic, just run pkg-static to upgrade pkg it-self
>> 
>> /usr/local/sbin/pkg-static install -f pkg
>> 
> 
> I think that these instructions should be in the announcement release notes 
> as this question comes up a lot. The notes just say something like "upgrade 
> all your packages". Most people will then just try and run pkg upgrade and 
> get that error without knowing how to solve it. It's not intuitive unless you 
> have come across this before.
> 
> -- 
> Matt
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Jenkins build is still unstable: FreeBSD_stable_10 #432

2016-10-19 Thread jenkins-admin 
https://jenkins.FreeBSD.org/job/FreeBSD_stable_10/432/
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.0 Install Question

2016-10-19 Thread Guido Falsi 
On 10/19/16 11:37, Miroslav Lachman wrote:
> Matthew Seaman wrote on 2016/10/19 11:08:
>> On 2016/10/19 09:55, Matt Smith wrote:
>>> On Oct 19 10:38, Miroslav Lachman wrote:
 Jonathan Haack wrote on 2016/10/19 10:09:
> Awe geez ... pkg won't work ... says "shared object "libssl.so.7" not
> found, required by "pkg"

 Do not panic, just run pkg-static to upgrade pkg it-self

 /usr/local/sbin/pkg-static install -f pkg

>>>
>>> I think that these instructions should be in the announcement release
>>> notes as this question comes up a lot. The notes just say something like
>>> "upgrade all your packages". Most people will then just try and run pkg
>>> upgrade and get that error without knowing how to solve it. It's not
>>> intuitive unless you have come across this before.
>>
>> pkg(8) does have a built-in warning when it detects an OS major version
>> upgrade, which is to do a forced upgrade of pkg(8) so it matches the ABI
>> versions of system shlibs.  Did that warning appear in this case?
> 
> I think it is not shown if pkg is missing some libraries.
> It is shown when OS major version changes and you run pkg befor old
> libraries are deleted or if you run pkg-static:
> 
> pkg-static: Warning: Major OS version upgrade detected.  Running
> "pkg-static install -f pkg" recommended
> 

The correct procedure (and I think it's documented somewhere) is to run
"pkg upgrade -f" before removing the old libraries.

If compiling from sources that is before make delete-old-libraries and
is explicitly stated when running make delete-old to upgrade ports
before going on.

If upgrading using freebsd-update that's before running "freebsd-update
install" for the third time(if I remember correctly) and I think I
remember freebsd-update stating something about upgrading installed
packages, but I'm not 100% sure.

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

VT not showing cyrillic characters in text mode

2016-10-19 Thread adg 

Hello everyone.

Cannot figure out if vt console driver supports non-ansi characters when 
started in textmode. The font in sys/dev/vt/vt_font_default.c seems to 
include cyrillic glyphs, but either it is not being used in textmode or 
something else is broken since only '?' are displayed instead of proper 
symbols. The LANG/LC_ALL doesn't affect anything. The problem occurs on 
11.0-RELEASE and 10.3-RELEASE.
Textmode is required for me since vt performance in graphical mode is 
very poor on HyperV and textmode looks like the only option.


(sorry about the previous messy messages in this mailing list, didnt 
expect problems with html emails ;)


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

Re: 11.0 Install Question

2016-10-19 Thread Miroslav Lachman 

Matthew Seaman wrote on 2016/10/19 11:08:

On 2016/10/19 09:55, Matt Smith wrote:

On Oct 19 10:38, Miroslav Lachman wrote:

Jonathan Haack wrote on 2016/10/19 10:09:

Awe geez ... pkg won't work ... says "shared object "libssl.so.7" not
found, required by "pkg"


Do not panic, just run pkg-static to upgrade pkg it-self

/usr/local/sbin/pkg-static install -f pkg



I think that these instructions should be in the announcement release
notes as this question comes up a lot. The notes just say something like
"upgrade all your packages". Most people will then just try and run pkg
upgrade and get that error without knowing how to solve it. It's not
intuitive unless you have come across this before.


pkg(8) does have a built-in warning when it detects an OS major version
upgrade, which is to do a forced upgrade of pkg(8) so it matches the ABI
versions of system shlibs.  Did that warning appear in this case?


I think it is not shown if pkg is missing some libraries.
It is shown when OS major version changes and you run pkg befor old 
libraries are deleted or if you run pkg-static:


pkg-static: Warning: Major OS version upgrade detected.  Running 
"pkg-static install -f pkg" recommended


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

Re: 11.0 Install Question

2016-10-19 Thread Matthew Seaman 
On 2016/10/19 09:55, Matt Smith wrote:
> On Oct 19 10:38, Miroslav Lachman wrote:
>> Jonathan Haack wrote on 2016/10/19 10:09:
>>> Awe geez ... pkg won't work ... says "shared object "libssl.so.7" not
>>> found, required by "pkg"
>>
>> Do not panic, just run pkg-static to upgrade pkg it-self
>>
>> /usr/local/sbin/pkg-static install -f pkg
>>
> 
> I think that these instructions should be in the announcement release
> notes as this question comes up a lot. The notes just say something like
> "upgrade all your packages". Most people will then just try and run pkg
> upgrade and get that error without knowing how to solve it. It's not
> intuitive unless you have come across this before.

pkg(8) does have a built-in warning when it detects an OS major version
upgrade, which is to do a forced upgrade of pkg(8) so it matches the ABI
versions of system shlibs.  Did that warning appear in this case?

Cheers,

Matthew







signature.asc
Description: OpenPGP digital signature

Re: 11.0 Install Question

2016-10-19 Thread Matt Smith 

On Oct 19 10:38, Miroslav Lachman wrote:

Jonathan Haack wrote on 2016/10/19 10:09:

Awe geez ... pkg won't work ... says "shared object "libssl.so.7" not found, required by 
"pkg"


Do not panic, just run pkg-static to upgrade pkg it-self

/usr/local/sbin/pkg-static install -f pkg



I think that these instructions should be in the announcement release 
notes as this question comes up a lot. The notes just say something like 
"upgrade all your packages". Most people will then just try and run pkg 
upgrade and get that error without knowing how to solve it. It's not 
intuitive unless you have come across this before.


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

Re: 11.0 Install Question

2016-10-19 Thread Miroslav Lachman 

Jonathan Haack wrote on 2016/10/19 10:09:

Awe geez ... pkg won't work ... says "shared object "libssl.so.7" not found, required by 
"pkg"


Do not panic, just run pkg-static to upgrade pkg it-self

/usr/local/sbin/pkg-static install -f pkg

Miroslav Lachman

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

Re: 11.0 Install Question

2016-10-19 Thread Jonathan Haack 
Thanks - worked then reinstalled pkg with force






Sincerely,

Coach Haack

DP Coordinator, Mandela International Magnet School
Board of Directors, First Serve NM
President, NMCTM

www.jonathanhaack.com

"It is better to have tried and failed than to have succeeded at doing 
nothing." 

Confidentiality Notice:  This email, including all attachments is for the sole 
use of the intended recipient or recipients and may contain confidential 
information.  Any unauthorized review, use, disclosure, or distribution, is 
prohibited unless specifically provided under the New Mexico Inspection of 
Public Records Act.  If you are not the intended recipient, please contact the 
sender and destroy all copies of this message.

> On Oct 19, 2016, at 2:10 AM, Warner Losh  wrote:
> 
> Try pkg-static.
> 
>> On Wed, Oct 19, 2016 at 2:09 AM, Jonathan Haack  wrote:
>> Awe geez ... pkg won't work ... says "shared object "libssl.so.7" not found, 
>> required by "pkg"
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> Sincerely,
>> 
>> Coach Haack
>> 
>> DP Coordinator, Mandela International Magnet School
>> Board of Directors, First Serve NM
>> President, NMCTM
>> 
>> www.jonathanhaack.com
>> 
>> "It is better to have tried and failed than to have succeeded at doing 
>> nothing."
>> 
>> Confidentiality Notice:  This email, including all attachments is for the 
>> sole use of the intended recipient or recipients and may contain 
>> confidential information.  Any unauthorized review, use, disclosure, or 
>> distribution, is prohibited unless specifically provided under the New 
>> Mexico Inspection of Public Records Act.  If you are not the intended 
>> recipient, please contact the sender and destroy all copies of this message.
>> 
>>> On Oct 19, 2016, at 12:49 AM, Christopher Hall 
>>>  wrote:
>>> 
>>> Hello Jonathan,
>>> 
>>> On Tue, 18 Oct 2016 23:06:10 -0600, Jonathan Haack 
>>> wrote:
>>> 
 I am running 10.1 fully update with
 
 freebsd-update fetch
 freebsd-update install
 
 then, every time I do
 
 freebsd-update -r upgrade 11.0-RELEASE
 
 It says it failed an integrity check and cowardly refuses … I have
 followed all forum advise and upgraded pkg, rebooted ran everything
 again and again … cowardly fails each time
 
 any way to force / and or re-download and do over?
>>> 
>>> I just noticed a line that appears to zero out bspatch in the procedure
>>> on:
>>>https://www.freebsd.org/releases/11.0R/announce.html
>>> Have you tried that?
>>> 
 
 
 Sincerely,
 
 Coach Haack
>>> 
>>> --
>>> Best Regards.
>>> Christopher Hall.
>> ___
>> freebsd-stable@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.0 Install Question

2016-10-19 Thread Warner Losh 
Try pkg-static.

On Wed, Oct 19, 2016 at 2:09 AM, Jonathan Haack  wrote:
> Awe geez ... pkg won't work ... says "shared object "libssl.so.7" not found, 
> required by "pkg"
>
>
>
>
>
>
>
>
> Sincerely,
>
> Coach Haack
>
> DP Coordinator, Mandela International Magnet School
> Board of Directors, First Serve NM
> President, NMCTM
>
> www.jonathanhaack.com
>
> "It is better to have tried and failed than to have succeeded at doing 
> nothing."
>
> Confidentiality Notice:  This email, including all attachments is for the 
> sole use of the intended recipient or recipients and may contain confidential 
> information.  Any unauthorized review, use, disclosure, or distribution, is 
> prohibited unless specifically provided under the New Mexico Inspection of 
> Public Records Act.  If you are not the intended recipient, please contact 
> the sender and destroy all copies of this message.
>
>> On Oct 19, 2016, at 12:49 AM, Christopher Hall 
>>  wrote:
>>
>> Hello Jonathan,
>>
>> On Tue, 18 Oct 2016 23:06:10 -0600, Jonathan Haack 
>> wrote:
>>
>>> I am running 10.1 fully update with
>>>
>>> freebsd-update fetch
>>> freebsd-update install
>>>
>>> then, every time I do
>>>
>>> freebsd-update -r upgrade 11.0-RELEASE
>>>
>>> It says it failed an integrity check and cowardly refuses … I have
>>> followed all forum advise and upgraded pkg, rebooted ran everything
>>> again and again … cowardly fails each time
>>>
>>> any way to force / and or re-download and do over?
>>
>> I just noticed a line that appears to zero out bspatch in the procedure
>> on:
>> https://www.freebsd.org/releases/11.0R/announce.html
>> Have you tried that?
>>
>>>
>>>
>>> Sincerely,
>>>
>>> Coach Haack
>>
>> --
>> Best Regards.
>> Christopher Hall.
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.0 Install Question

2016-10-19 Thread Jonathan Haack 
Awe geez ... pkg won't work ... says "shared object "libssl.so.7" not found, 
required by "pkg"








Sincerely,

Coach Haack

DP Coordinator, Mandela International Magnet School
Board of Directors, First Serve NM
President, NMCTM

www.jonathanhaack.com

"It is better to have tried and failed than to have succeeded at doing 
nothing." 

Confidentiality Notice:  This email, including all attachments is for the sole 
use of the intended recipient or recipients and may contain confidential 
information.  Any unauthorized review, use, disclosure, or distribution, is 
prohibited unless specifically provided under the New Mexico Inspection of 
Public Records Act.  If you are not the intended recipient, please contact the 
sender and destroy all copies of this message.

> On Oct 19, 2016, at 12:49 AM, Christopher Hall 
>  wrote:
> 
> Hello Jonathan,
> 
> On Tue, 18 Oct 2016 23:06:10 -0600, Jonathan Haack 
> wrote:
> 
>> I am running 10.1 fully update with 
>> 
>> freebsd-update fetch
>> freebsd-update install
>> 
>> then, every time I do 
>> 
>> freebsd-update -r upgrade 11.0-RELEASE
>> 
>> It says it failed an integrity check and cowardly refuses … I have
>> followed all forum advise and upgraded pkg, rebooted ran everything
>> again and again … cowardly fails each time
>> 
>> any way to force / and or re-download and do over?
> 
> I just noticed a line that appears to zero out bspatch in the procedure
> on: 
> https://www.freebsd.org/releases/11.0R/announce.html
> Have you tried that?
> 
>> 
>> 
>> Sincerely,
>> 
>> Coach Haack
> 
> -- 
> Best Regards.
> Christopher Hall.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.0 Install Question

2016-10-19 Thread Jonathan Haack 
Hey guys ... I got impatient after so many tries that I decided to step to 10.3 
first ... that went perfectly and now it is completed the kernel phase of 11.0 
... not sure why it wouldn't hop to 11 straight from 10.1 ... I found some 
people with same forum and I assure you I had latest patches because it was a 
clean install production machine built off a brand new .iso ... so?  Oh well 
sorry can't help debug more since mine is now updating ... thanks for the help 
guys






Sincerely,

Coach Haack

DP Coordinator, Mandela International Magnet School
Board of Directors, First Serve NM
President, NMCTM

www.jonathanhaack.com

"It is better to have tried and failed than to have succeeded at doing 
nothing." 

Confidentiality Notice:  This email, including all attachments is for the sole 
use of the intended recipient or recipients and may contain confidential 
information.  Any unauthorized review, use, disclosure, or distribution, is 
prohibited unless specifically provided under the New Mexico Inspection of 
Public Records Act.  If you are not the intended recipient, please contact the 
sender and destroy all copies of this message.

> On Oct 19, 2016, at 12:49 AM, Christopher Hall 
>  wrote:
> 
> Hello Jonathan,
> 
> On Tue, 18 Oct 2016 23:06:10 -0600, Jonathan Haack 
> wrote:
> 
>> I am running 10.1 fully update with 
>> 
>> freebsd-update fetch
>> freebsd-update install
>> 
>> then, every time I do 
>> 
>> freebsd-update -r upgrade 11.0-RELEASE
>> 
>> It says it failed an integrity check and cowardly refuses … I have
>> followed all forum advise and upgraded pkg, rebooted ran everything
>> again and again … cowardly fails each time
>> 
>> any way to force / and or re-download and do over?
> 
> I just noticed a line that appears to zero out bspatch in the procedure
> on: 
> https://www.freebsd.org/releases/11.0R/announce.html
> Have you tried that?
> 
>> 
>> 
>> Sincerely,
>> 
>> Coach Haack
> 
> -- 
> Best Regards.
> Christopher Hall.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Nightly disk-related panic since upgrade to 10.3

2016-10-19 Thread Andrea Venturoli 

Hello.

Last week I upgraded a 9.3/amd64 box to 10.3: since then, it crashed and 
rebooted at least once every night.


The only exception was on Friday, when it locked without rebooting: it 
still answered ping request and logins through HTTP would half work; I'm 
under the impression that the disk subsystem was hung, so ICMP would 
work since it does no I/O and HTTP too worked as far as no disk access 
was required.


Today I was able to get a couple of (almost identical) dumps:


cpuid = 1
KDB: stack backtrace:
#0 0x804ee170 at kdb_backtrace+0x60
#1 0x804b4576 at vpanic+0x126
#2 0x804b4443 at panic+0x43
#3 0x8068fd2a at softdep_deallocate_dependencies+0x6a
#4 0x805394b5 at brelse+0x145
#5 0x8053793c at bufwrite+0x3c
#6 0x806ae20f at ffs_write+0x3df
#7 0x8076d519 at VOP_WRITE_APV+0x149
#8 0x806ec7c9 at vnode_pager_generic_putpages+0x2a9
#9 0x8076f3b7 at VOP_PUTPAGES_APV+0xa7
#10 0x806ea6f5 at vnode_pager_putpages+0xc5
#11 0x806e17f8 at vm_pageout_flush+0xc8
#12 0x806db432 at vm_object_page_collect_flush+0x182
#13 0x806db1cd at vm_object_page_clean+0x13d
#14 0x806dadbe at vm_object_terminate+0x8e
#15 0x806eac60 at vnode_destroy_vobject+0x90
#16 0x806b4232 at ufs_reclaim+0x22
#17 0x8076e5c7 at VOP_RECLAIM_APV+0xa7




Has anyone any better insight on what might be going on?
The disks are all connected to a SAS RAID adapter running on mfi; I 
don't think it might be an hardware issue, since it has worked perfectly 
for years until I did the upgrade; also mfiutil says everything is ok 
and nothing mfi-related is in the logs.




Some ideas come to mind about which I might use a second opinion:

_ soft-update is broken: that would really surprise me, since I've been 
using that for years on this and several other boxes (10.3 too);


_ snapshot creation/deletion is causing this: again I'm using that 
almost anywhere, so I don't think this might be the cause alone; 
besides, I've been able to do some dumps without trouble and I don't 
think anything was messing with snapshots at the time of the last two 
panics;


_ mfi driver is broken on 10.3: this is more reasonable to me, since 
this is the only machine I have it on and it's the only case where I get 
this panics.
I found https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183618, but I 
get no "g_vfs_done()..." messages.


Any other hint?



I'd really like to find out what's going on, I'll appreciate any help 
and I'm willing to provide any useful info.


On the other hand, this is a production server, so I have to solve this 
really soon.
Some idea comes to mind, like disabling softupdate (knowing which file 
system was having trouble would help here; is there any way to know?), 
trying to enable journaling, upgrading to 10-STABLE, build a kernel with 
INVARIANTS/WITNESS/etc..., but I'd appreciate a second opinion before I 
start shooting in the dark.




 bye & Thanks
av.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.0 Install Question

2016-10-19 Thread Christopher Hall 
Hello Jonathan,

On Tue, 18 Oct 2016 23:06:10 -0600, Jonathan Haack 
wrote:

> I am running 10.1 fully update with 
> 
> freebsd-update fetch
> freebsd-update install
> 
> then, every time I do 
> 
> freebsd-update -r upgrade 11.0-RELEASE
> 
> It says it failed an integrity check and cowardly refuses … I have
> followed all forum advise and upgraded pkg, rebooted ran everything
> again and again … cowardly fails each time
> 
> any way to force / and or re-download and do over?

I just noticed a line that appears to zero out bspatch in the procedure
on: 
 https://www.freebsd.org/releases/11.0R/announce.html
Have you tried that?

> 
> 
> Sincerely,
> 
> Coach Haack

-- 
Best Regards.
Christopher Hall.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.0 Install Question

2016-10-19 Thread Holger Kipp 
Dear Jonathan,

On 19 Oct 2016, at 08:08, Jonathan Haack 
> wrote:

I am running 10.1 fully update with

freebsd-update fetch
freebsd-update install

then, every time I do

freebsd-update -r upgrade 11.0-RELEASE

It says it failed an integrity check and cowardly refuses … I have followed all 
forum advise and upgraded pkg, rebooted ran everything again and again … 
cowardly fails each time

According to
https://www.freebsd.org/releases/11.0R/installation.html
this should work.

However to give any help or advise you might want to post the exact output and 
integrity check information on this list first, as well as your current FreeBSD 
Version (freebsd-version -ku)

Just in case - you have already backed up all your valuable data and current 
config-files?

Best regards,
Holger

any way to force / and or re-download and do over?


Sincerely,

Coach Haack

DP Coordinator, Mandela International Magnet School
Board of Directors, First Serve NM
President, NMCTM

www.jonathanhaack.com

"It is better to have tried and failed than to have succeeded at doing nothing."
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

11.0 Install Question

2016-10-19 Thread Jonathan Haack 
I am running 10.1 fully update with 

freebsd-update fetch
freebsd-update install

then, every time I do 

freebsd-update -r upgrade 11.0-RELEASE

It says it failed an integrity check and cowardly refuses … I have followed all 
forum advise and upgraded pkg, rebooted ran everything again and again … 
cowardly fails each time

any way to force / and or re-download and do over?




Sincerely,

Coach Haack

DP Coordinator, Mandela International Magnet School
Board of Directors, First Serve NM
President, NMCTM

www.jonathanhaack.com

"It is better to have tried and failed than to have succeeded at doing 
nothing." 

Confidentiality Notice:  This email, including all attachments is for the sole 
use of the intended recipient or recipients and may contain confidential 
information.  Any unauthorized review, use, disclosure, or distribution, is 
prohibited unless specifically provided under the New Mexico Inspection of 
Public Records Act.  If you are not the intended recipient, please contact the 
sender and destroy all copies of this message.




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