Two USB 4 disk enclosure and a panic

2018-04-23 Thread Nenhum_de_Nos 
Hi,

I would like to know how to debug this. I have two 4 disk enclosures:

Mediasonic ProBox 4 Bay 3.5' SATA HDD Enclosure – USB 3.0 & eSATA (HF2-SU3S2)
NexStar HX4 - NST-640SU3-BK

and both have 4 disk on them, and not all disk are equal.

The issue comes when I plug the probox usb3 enclosure on the system. I
can't even read the /var/log/message, it crashes very quickly.

I can see on the boot process up to the point where the second enclosure
comes to be loaded. The 4 disk are shown on the dmesg/console, and then a
core dump happens, the boot process goes to the debug screen and a restart
happens like a flash.

The motherboard is a Intel® Desktop Board D525MW running 8GB RAM.
All disk use ZFS, 4 or 5 zpools, one raidz, one mirror and two or three
single disk pools.
FreeBSD xxx 11.1-RELEASE-p7 FreeBSD 11.1-RELEASE-p7 #1 r330596: Thu Mar  8
06:45:59 -03 2018 root@xxx:/usr/obj/usr/src/sys/FreeBSD-11-amd64-PF 
amd64

The kernel is a slightly modified generic, just to have altq.

How can I debug this? I have no idea. I have to use two machines to run
all those disks, and I would really like to have just one for it.

Can it be the amount of RAM? The other box is and APU2 from PCEngines and
have 4GB ram. apu2 uname -a: FreeBSD yyy 11.1-RELEASE-p4 FreeBSD
11.1-RELEASE-p4 #0: Tue Nov 14 06:12:40 UTC 2017
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

I tried to plug the Vantec hardware on the apu2 box, but there it would
not panic, but won't load all vantec disks neither. I really run out of
ideas here :(

thanks.

-- 
"We will call you Cygnus,
the God of balance you shall be."

___
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: What should do in chrooted environment?

2018-04-23 Thread O'Connor, Daniel 


> On 24 Apr 2018, at 08:14, Glen Barber  wrote:
> I think you might not have the devfs mount in the image.  With the paths
> provided above, I think this should fix it:
> 
> # mount -t devfs devfs /mnt/dev

I wonder if it's worth doing a basic sanity check that /dev/null and /dev/zero 
look like device nodes.

I've made this mistake too and it produces some very confusing error messages :(

--
Daniel O'Connor
"The nice thing about standards is that there
are so many of them to choose from."
 -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C

___
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: What should do in chrooted environment?

2018-04-23 Thread Glen Barber 
On Tue, Apr 24, 2018 at 07:28:06AM +0900, KIRIYAMA Kazuhiko wrote:
> Hi, all
> 
> I've make buildworld in chrooted environment. But failed at
> 'stage 4.2: building libraries' [1]:
> 
> objcopy --only-keep-debug libproc.so.3.full libproc.so.3.debug
> objcopy --strip-debug --add-gnu-debuglink=libproc.so.3.debug  
> libproc.so.3.full libproc.so.3
> sh /usr/src/tools/install.sh  -C -o root -g wheel -m 444   libproc.a 
> /usr/obj/usr/src/tmp/usr/lib/
> sh /usr/src/tools/install.sh  -s -o root -g wheel -m 444 libproc.so.3 
> /usr/obj/usr/src/tmp/usr/lib/
> sh /usr/src/tools/install.sh  -o root -g wheel -m 444libproc.so.3.debug 
> /usr/obj/usr/src/tmp/usr/lib/debug/usr/lib/
> sh /usr/src/tools/install.sh -l rs  libproc.so.3 
> /usr/obj/usr/src/tmp/usr/lib/libproc.so
> sh /usr/src/tools/install.sh  -C -o root -g wheel -m 444  
> /usr/src/lib/libproc/libproc.h /usr/obj/usr/src/tmp/usr/include/
> make[5]: "/dev/null" line 1: Need an operator
> make[5]: Fatal errors encountered -- cannot continuemake[4]: 
> "/usr/src/Makefile.inc1" line 421: warning: "MK_AUTO_OBJ=no MAKEFLAGS= 
> CPUTYPE=dummy make  -f /dev/null -m /usr/src/share/mk -V CPUTYPE" returned 
> non-zero status
> make[4]: "/usr/src/Makefile.inc1" line 423: CPUTYPE global should be set with 
> ?=.
> *** Error code 1
> 
> Stop.
> make[3]: stopped in /usr/src
> *** Error code 1
> 
> Stop.
> make[2]: stopped in /usr/src
> *** Error code 1
> 
> Stop.
> make[1]: stopped in /usr/src
> 
> My chrooted environment is a bhyve vm attach & mounted one
> like this(*1):
> 
> root@vms:~ # mdconfig  -a -t vnode -f /vm/tbedfs/disk0.img 
> md0
> root@vms:~ # gpart show md0
> =>  40  16777136  md0  GPT  (8.0G)
> 4024   - free -  (12K)
> 64  10241  freebsd-boot  (512K)
>   1088  167760232  freebsd-ufs  (8.0G)
>   1677711141   - free -  (21K)
>   16777152233  freebsd-swap  (12K)
>   16777175 1   - free -  (512B)
> 
> root@vms:~ # mount /dev/md0p2 /mnt
> 
> 
> And src and obj are nullfs mounted to latest src
> repository(r332874) and OBJDIR respectively:
> 
> 
> root@vms:~ # uname -a
> FreeBSD vms.pis 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r331153: Tue Mar 20 
> 10:13:56 JST 2018 
> ad...@t.pis:/ds/obj/current/12.0/r331153/ds/src/current/12.0/r331153/amd64.amd64/sys/GENERIC
>   amd64
> root@vms:~ # 
> admin@vms:~ % df
> Filesystem1K-blocks Used   Avail Capacity  
> Mounted on
> /dev/aacd0p4   10143484  4624840 470716850%/
> devfs 11   0   100%/dev
> /dev/aacd0p514560423728 79273144 13316316688 1%/ds
> /ds/.dake   14560423728 79273144 13316316688 1%/.dake
> /ds/vm  14560423728 79273144 13316316688 1%/vm
> /dev/md0p2  5061084  3053316 160288466%/mnt
> /ds/src/stable/11.1/r332874 14560423728 79273144 13316316688 1%
> /mnt/usr/src
> /ds/obj/stable/11.1/r332874 14560423728 79273144 13316316688 1%
> /mnt/usr/obj
> admin@vms:~ % 
> 
> 
> Then chroot to /mnt and make buildworld:
> 
> 
> root@vms:~ # chroot /mnt "make buildworld"
> 
> 
> Of course 'make buildworld' in vm was successfully finished [2]:
> 
> 
> admin@tbedfs:~ % uname -a
> FreeBSD tbedfs 11.1-STABLE FreeBSD 11.1-STABLE #0 r332428: Thu Apr 12 
> 16:37:51 UTC 2018 
> r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
> admin@tbedfs:~ % df
> Filesystem1K-blocks Used   Avail Capacity 
>  Mounted on
> /dev/vtbd0p28106116   849980 660764811%   
>  /
> devfs 11   0   100%   
>  /dev
> vms.pis:/.dake  14560423728 83720204 13311869628 1%   
>  /.dake
> vms.pis:/ds/src/stable/11.1/r332874 14560423728 83720204 13311869628 1%   
>  /usr/src
> vms.pis:/ds/obj/stable/11.1/r332874 14560423728 83720204 13311869628 1%   
>  /usr/obj
> admin@tbedfs:~ % su
> Password:
> root@tbedfs:/usr/home/admin # cd /usr/src/
> root@tbedfs:/usr/src # make buildworld
> 
> 
> To make buildworld in chrooted environment, what should I do ?
> 

I think you might not have the devfs mount in the image.  With the paths
provided above, I think this should fix it:

 # mount -t devfs devfs /mnt/dev

Glen



signature.asc
Description: PGP signature

What should do in chrooted environment?

2018-04-23 Thread KIRIYAMA Kazuhiko 
Hi, all

I've make buildworld in chrooted environment. But failed at
'stage 4.2: building libraries' [1]:

objcopy --only-keep-debug libproc.so.3.full libproc.so.3.debug
objcopy --strip-debug --add-gnu-debuglink=libproc.so.3.debug  libproc.so.3.full 
libproc.so.3
sh /usr/src/tools/install.sh  -C -o root -g wheel -m 444   libproc.a 
/usr/obj/usr/src/tmp/usr/lib/
sh /usr/src/tools/install.sh  -s -o root -g wheel -m 444 libproc.so.3 
/usr/obj/usr/src/tmp/usr/lib/
sh /usr/src/tools/install.sh  -o root -g wheel -m 444libproc.so.3.debug 
/usr/obj/usr/src/tmp/usr/lib/debug/usr/lib/
sh /usr/src/tools/install.sh -l rs  libproc.so.3 
/usr/obj/usr/src/tmp/usr/lib/libproc.so
sh /usr/src/tools/install.sh  -C -o root -g wheel -m 444  
/usr/src/lib/libproc/libproc.h /usr/obj/usr/src/tmp/usr/include/
make[5]: "/dev/null" line 1: Need an operator
make[5]: Fatal errors encountered -- cannot continuemake[4]: 
"/usr/src/Makefile.inc1" line 421: warning: "MK_AUTO_OBJ=no MAKEFLAGS= 
CPUTYPE=dummy make  -f /dev/null -m /usr/src/share/mk -V CPUTYPE" returned 
non-zero status
make[4]: "/usr/src/Makefile.inc1" line 423: CPUTYPE global should be set with 
?=.
*** Error code 1

Stop.
make[3]: stopped in /usr/src
*** Error code 1

Stop.
make[2]: stopped in /usr/src
*** Error code 1

Stop.
make[1]: stopped in /usr/src

My chrooted environment is a bhyve vm attach & mounted one
like this(*1):

root@vms:~ # mdconfig  -a -t vnode -f /vm/tbedfs/disk0.img 
md0
root@vms:~ # gpart show md0
=>  40  16777136  md0  GPT  (8.0G)
4024   - free -  (12K)
64  10241  freebsd-boot  (512K)
  1088  167760232  freebsd-ufs  (8.0G)
  1677711141   - free -  (21K)
  16777152233  freebsd-swap  (12K)
  16777175 1   - free -  (512B)

root@vms:~ # mount /dev/md0p2 /mnt


And src and obj are nullfs mounted to latest src
repository(r332874) and OBJDIR respectively:


root@vms:~ # uname -a
FreeBSD vms.pis 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r331153: Tue Mar 20 
10:13:56 JST 2018 
ad...@t.pis:/ds/obj/current/12.0/r331153/ds/src/current/12.0/r331153/amd64.amd64/sys/GENERIC
  amd64
root@vms:~ # 
admin@vms:~ % df
Filesystem1K-blocks Used   Avail Capacity  Mounted 
on
/dev/aacd0p4   10143484  4624840 470716850%/
devfs 11   0   100%/dev
/dev/aacd0p514560423728 79273144 13316316688 1%/ds
/ds/.dake   14560423728 79273144 13316316688 1%/.dake
/ds/vm  14560423728 79273144 13316316688 1%/vm
/dev/md0p2  5061084  3053316 160288466%/mnt
/ds/src/stable/11.1/r332874 14560423728 79273144 13316316688 1%
/mnt/usr/src
/ds/obj/stable/11.1/r332874 14560423728 79273144 13316316688 1%
/mnt/usr/obj
admin@vms:~ % 


Then chroot to /mnt and make buildworld:


root@vms:~ # chroot /mnt "make buildworld"


Of course 'make buildworld' in vm was successfully finished [2]:


admin@tbedfs:~ % uname -a
FreeBSD tbedfs 11.1-STABLE FreeBSD 11.1-STABLE #0 r332428: Thu Apr 12 16:37:51 
UTC 2018 r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
admin@tbedfs:~ % df
Filesystem1K-blocks Used   Avail Capacity  
Mounted on
/dev/vtbd0p28106116   849980 660764811%/
devfs 11   0   100%
/dev
vms.pis:/.dake  14560423728 83720204 13311869628 1%
/.dake
vms.pis:/ds/src/stable/11.1/r332874 14560423728 83720204 13311869628 1%
/usr/src
vms.pis:/ds/obj/stable/11.1/r332874 14560423728 83720204 13311869628 1%
/usr/obj
admin@tbedfs:~ % su
Password:
root@tbedfs:/usr/home/admin # cd /usr/src/
root@tbedfs:/usr/src # make buildworld


To make buildworld in chrooted environment, what should I do ?

Best regards

(*1) Acctually used vm-bhyve port(sysutils/vm-bhyve).
[1] http://ds.truefc.org/~kiri/freebsd/stable/dake.log
[2] http://ds.truefc.org/~kiri/freebsd/stable/make_buildworld.log

---
KIRIYAMA Kazuhiko
___
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: Ryzen issues on FreeBSD ? (with sort of workaround)

2018-04-23 Thread Don Lewis 
On 23 Apr, Mike Tancsa wrote:
> On 4/22/2018 5:29 PM, Don Lewis wrote:
>> Pretty much all of my BIOS settings are the defaults.
>> 
>> I suspect that the idle hang issues are motherboard and/or BIOS
>> specific.  For the record my motherboard is a Gigabyte
>> GA-AX370-Gaming 5.
> Hi Don,
>   Any chance you could try that bhyve test ? Basically, or 3 VMs and then
> run iperf3 between the instances.  I can lock up all 3 of my AMD boards
> (2 ASUS, one MSI) and both my Epyc (SuperMicro) boards.

I should be able to do that, but it will likely be a few days before I
can get around to it.

___
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: Ryzen issues on FreeBSD ? (with sort of workaround)

2018-04-23 Thread Mike Tancsa 
On 4/22/2018 5:29 PM, Don Lewis wrote:
> Pretty much all of my BIOS settings are the defaults.
> 
> I suspect that the idle hang issues are motherboard and/or BIOS
> specific.  For the record my motherboard is a Gigabyte
> GA-AX370-Gaming 5.
Hi Don,
Any chance you could try that bhyve test ? Basically, or 3 VMs and then
run iperf3 between the instances.  I can lock up all 3 of my AMD boards
(2 ASUS, one MSI) and both my Epyc (SuperMicro) boards.

---Mike

-- 
---
Mike Tancsa, tel +1 519 651 3400 x203
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada
___
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: Ryzen issues on FreeBSD ? (with sort of workaround)

2018-04-23 Thread Pete French 
> fairly pleased with that. Am going to try the test case that Mike Tancsa
> posted to see if I can get it to lockup today though,. now that I am in
> front of it to reset of required. Will report results either way...

So, I have been ran the iperf scripts all day (about 4 hours now) with
the Ryzen box being the reciever and another BSD box as the sender. I
had re-enabled SMT on the Ryzen box out of curiosity.

All worked fine until just no,w when it did lockup. But the lockup
happened when I fired up VirtualBox as well on the Ryzen machine, had that
doing a lot of disc activity and also did a lot of ZFS activity on the box
itself. Which I find interesting, because your lockups were also happenng
when VirtualBox was running were they not ?

So, am going to try that again (the iperf test and simultaneous Win10
in VirtualBox), but with SMT off, to see if I can reproduce it.

-pete.

___
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: Ryzen issues on FreeBSD ? (with sort of workaround)

2018-04-23 Thread Pete French 
> I have a Ryzen system
> parts: https://pcpartpicker.com/list/HhycYT
> dmesg: http://dmesgd.nycbug.org/index.cgi?do=view=3516
>
> which I have been using for months without issue and on completely
> default settings.

Thats encouranging -= and I think you are the first person to report
that without any tweaking to the best of my recollection!

> What mobo do you have? Did you update the BIOS to the latest version?

MSI X370 Xpower Titanium - I upgraded to that one from my original choice
ater comments on this thread about power  which I hadnt considered (I
had also decided to buy a larger Ryzen 7). The BIOS is the latest version,
and I cleared CMOS to get the default settings. Memory is some Crucial
DDR4 3200 which is underclocked to 2133. This microprocessor itself
is a Ryzen 7 1700 (not X) which was made in week 33, so should not have the
hardware fault on it.

It's been stable over the weekend, as I posted in a different email, am
going to try and knock it over today with some tests if I can.

-pete.
___
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: Ryzen issues on FreeBSD ? (with sort of workaround)

2018-04-23 Thread Pete French 
> And of course now that we say something about it, I get a lockup
> overnight...

Sods law I guess. Mine survived the weekend quite happily though, so am
fairly pleased with that. Am going to try the test case that Mike Tancsa
posted to see if I can get it to lockup today though,. now that I am in
front of it to reset of required. Will report results either way...

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