Re: Ver 2 of the patch [was: Re: i915 driver update testing]
On Fri, Oct 24, 2014 at 3:03 AM, Konstantin Belousov kostik...@gmail.com wrote: Due to my mistake during the patch generation, i915.5.patch is just a garbage. Use https://www.kib.kiev.ua/kib/drm/i915.6.patch. I already have one private report of the patch worked from person who got the same panic in iicbb. panic when I was opening Google maps in Chromium 38. But I was unable to reproduce it. The original code does not panic. src is r273588. CPU is an i5-3450. debug message attached. screenshot: https://lh3.googleusercontent.com/-BpPTfNTObtU/VEs9RGT7i6I/gfA/TvOnT-BP3zo/w894-h671-no/IMG_20141025_134906.jpg -Jia-Shiun. agp0: IvyBridge desktop GT1 IG on vgapci0 agp0: aperture size is 256M, detected 65532k stolen memory agp0: AGP_SNB_GFX_MODE: agp0: AGP_SNB_GCC1: 0x0211 agp0: Mappable GTT entries: 65536 agp0: Total GTT entries: 524288 info: [drm] Initialized drm 1.1.0 20060810 [drm:pid958:drm_probe] desc : (null) drmn0: Intel IvyBridge on vgapci0 [drm:pid958:drm_attach] MSI count = 1 vgapci0: attempting to allocate 1 MSI vectors (1 supported) msi: routing MSI IRQ 267 to local APIC 2 vector 51 vgapci0: using IRQ 267 for MSI info: [drm] MSI enabled 1 message(s) [drm:pid958:drm_load] [drm:pid958:drm_agp_init] agp_available = 1 info: [drm] AGP at 0xe000 256MB [drm:pid958:drm_ctxbitmap_next] bit : 0 [drm:pid958:drm_ctxbitmap_init] drm_ctxbitmap_init : 0 [drm:pid958:drm_addmap] offset = 0xf780, size = 0x0040, type = 1 [drm:pid958:drm_addmap] Added map 1 0xf780/0x40 [drm:pid958:intel_setup_mchbar] mchbar already enabled iicbus0: Philips I2C bus on iicbb0 addr 0xff iic0: I2C generic I/O on iicbus0 iic1: I2C generic I/O on iicbus1 iicbus2: Philips I2C bus on iicbb1 addr 0x0 iic2: I2C generic I/O on iicbus2 iic3: I2C generic I/O on iicbus3 iicbus4: Philips I2C bus on iicbb2 addr 0x0 iic4: I2C generic I/O on iicbus4 iic5: I2C generic I/O on iicbus5 iicbus6: Philips I2C bus on iicbb3 addr 0x0 iic6: I2C generic I/O on iicbus6 iic7: I2C generic I/O on iicbus7 iicbus8: Philips I2C bus on iicbb4 addr 0x0 iic8: I2C generic I/O on iicbus8 iic9: I2C generic I/O on iicbus9 iicbus10: Philips I2C bus on iicbb5 addr 0x0 iic10: I2C generic I/O on iicbus10 iic11: I2C generic I/O on iicbus11 iicbus12: Philips I2C bus on iicbb6 addr 0x0 iic12: I2C generic I/O on iicbus12 iic13: I2C generic I/O on iicbus13 [drm:pid958:intel_opregion_setup] graphic opregion physical addr: 0xd8a87018 [drm:pid958:intel_opregion_setup] SWSCI supported info: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). info: [drm] Driver supports precise vblank timestamp query. [drm:KMS:pid958:intel_detect_pch] Found PatherPoint PCH [drm:KMS:pid958:init_vbt_defaults] Set default to SSC at 100MHz [drm:KMS:pid958:intel_parse_bios] Using VBT from OpRegion: $VBT SNB/IVB-DESKTOPd [drm:KMS:pid958:parse_general_features] BDB_GENERAL_FEATURES int_tv_support 0 int_crt_support 1 lvds_use_ssc 0 lvds_ssc_freq 120 display_clock_mode 0 [drm:KMS:pid958:parse_general_definitions] crt_ddc_bus_pin: 2 [drm:KMS:pid958:parse_lfp_panel_data] Found panel mode in BIOS VBT tables: [drm:KMS:pid958:drm_mode_debug_printmodeline] Modeline 0:1024x768 0 65000 1024 1048 1184 1344 768 771 777 806 0x8 0xa [drm:KMS:pid958:parse_lfp_panel_data] VBT initial LVDS value 300 [drm:KMS:pid958:parse_sdvo_panel_data] Found SDVO panel mode in BIOS VBT tables: [drm:KMS:pid958:drm_mode_debug_printmodeline] Modeline 0:1600x1200 0 162000 1600 1664 1856 2160 1200 1201 1204 1250 0x8 0xa [drm:KMS:pid958:parse_sdvo_device_mapping] No SDVO device info is found in VBT [drm:KMS:pid958:intel_init_pm] Using MT version of forcewake [drm:KMS:pid958:intel_modeset_init] 3 display pipes available. [drm:KMS:pid958:intel_lvds_init] LVDS is not present in VBT [drm:KMS:pid958:intel_crt_init] pch crt adpa set to 0x80f40010 [drm:KMS:pid958:intel_setup_outputs] HDMIB 0 PCH_DP_B 0 HDMIC 1 HDMID 1 PCH_DP_C 1 PCH_DP_D 1 LVDS 0 [drm:KMS:pid958:intel_dp_i2c_init] i2c_init DPDDC-C [drm:KMS:pid958:intel_dp_aux_ch] dp_aux_ch timeout status 0x5145003f [drm:KMS:pid958:intel_dp_i2c_aux_ch] aux_ch failed -60 [drm:KMS:pid958:intel_dp_aux_ch] dp_aux_ch timeout status 0x5145003f [drm:KMS:pid958:intel_dp_i2c_aux_ch] aux_ch failed -60 [drm:KMS:pid958:intel_dp_i2c_init] i2c_init DPDDC-D [drm:KMS:pid958:intel_dp_aux_ch] dp_aux_ch timeout status 0x5145003f [drm:KMS:pid958:intel_dp_i2c_aux_ch] aux_ch failed -60 [drm:KMS:pid958:intel_dp_aux_ch] dp_aux_ch timeout status 0x5145003f [drm:KMS:pid958:intel_dp_i2c_aux_ch] aux_ch failed -60 [drm:KMS:pid958:ironlake_crtc_dpms] crtc 0/0 dpms off [drm:KMS:pid958:intel_update_fbc] [drm:KMS:pid958:ironlake_crtc_dpms] crtc 1/1 dpms off [drm:pid958:gm45_get_vblank_counter] i915: trying to get vblank count for disabled pipe B [drm:pid958:gm45_get_vblank_counter] i915: trying to get vblank count for disabled pipe B [drm:KMS:pid958:intel_update_fbc] [drm:KMS:pid958:ironlake_crtc_dpms] crtc 2/2 dpms off [drm:pid958:gm45_get_vblank_counter] i915: trying to get vblank
Some NFS server V4 questions
* 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: can't build CURRENT/amd64 using 9.3?
Garrett Cooper writes: The message is telling you (indirectly) that you need to run make buildworld successfully first? Recapping: Current system: FreeBSD 9.3-RELEASE #0 r268512: Fri Jul 11 03:13:02 UTC 2014 i386 Source tree at CURRENT/r273626. No make.conf. src.conf: KERNCONF=GENERIC TARGET=amd64 TARGET_ARCH=amd64 Build uses this script: #! /bin/sh cd /usr/src if [ -f buildworld.log ] then rm buildworld.log fi chflags -R noschg /usr/obj/* rm -rf /usr/obj make cleandir date ./buildworld.time make -j 1 TARGET=amd64 TARGET_ARCH=amd64 buildworld ./buildworld.log 21 tail -n 50 /usr/src/buildworld.log | sendmail huff Build log at http://users.rcn.com/roberthuff/bl.gz; So: is that or is it not a valid world build? Respectfully, Robert Huff ___ 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: can't build CURRENT/amd64 using 9.3?
On Fri, 2014-10-24 at 21:06 -0400, owner-freebsd-curr...@freebsd.org wrote: roberth...@rcn.com writes: I am now doing make buildkernel with TARGET/TARGET_ARCH on the command line. For installkernel, do I need to use them also, or will it magically know where to look? Kernel built. However: huff@ make installkernel ERROR: No kernel GENERIC to install. *** Error code 1 Stop. bmake: stopped in /usr/src *** [installkernel] Error code 1 Stop in /usr/src. huff@ make TARGET=amd64 TARGET_ARCH=amd64 installkernel ERROR: Please set DESTDIR! *** Error code 1 It appears you almost had it right at this point, but overlooked this error which is also the instructions of how to fix this error. Note that this error kept you from destroying your i386 build host by installing some amd64 bits on it. -- Ian Stop. bmake: stopped in /usr/src *** [installkernel] Error code 1 Stop in /usr/src. I believe there is a kernel in /usr/obj/amd64.amd64/usr/src/sys/GENERIC, and world in /usr/obj/amd64.amd64/usr/src. How do I make sure these get installed in the right place(s)? Respectfully, Robert Huff ___ 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: Some NFS server V4 questions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/25/14 03:07, Beeblebrox wrote:
* I can't get the NFS server to run V4 only. I have: sysctl
vfs.nfsd.server_min_nfsvers=4
[...]
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
Possibly need to arrange for mount_nfs to see -o nfsv4
(I use mount_nfs -o nfsv4,minorversion=1)
Then nfsstat shows eg:
terp:/library on /mnt/terp/library
nfsv4,minorversion=1,tcp,resvport,hard,cto,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=65536,wsize=65536,readdirsize=65536,readahead=1,wcommitsize=2798255,timeout=120,retrans=2147483647
HTH,
Russell
* 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
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBAgAGBQJUS8a3AAoJEFnLrGVSDFaEvWEP/iIKgw1kTmGQqgYAzVY++8uq
X3XMSnUFNGkyZSO/cz9gCO8S+oXkWVD8z3UbTKtyPCdTHhp48klTRW+ceSGvfhq2
oyWfcM5bXbOBLQZaoz66IL77mZHlWOTOLoGyNQZp7x/7KXETN7nK+qxQ1WDD7WM9
BW8fC+krQ4F5Tvqc70fylu93QKKUiqi26cOMWuRLTwgLXJY+NtPLMjH+SadDonNC
FvszjFpTsoP7cKPWA0vPA2iLb3Q43DT1+k23r6iY33JzTX2LW+zpzk+i4wEneNE8
JAgGqsFB08sH8krBrKo3n5+zcd5R0mZu3uX9a0CQJYiNHg6Phh4QgyETTYJT0ig/
mF1Q7V5z4FHLKdZigqO2WjNN2l2zfzDlUWfDTyc/b8CZIaPJemdqADsBVl76UdX8
2HspYZdAxR2zPc9EmpNPQJAksBFyUpwZy6cpHW+7wrkeeYoTWZLYV5sm4IscOzEE
tdof9VRIT+DGPrxLPFxO8tQiOV0eQWh3Om7Tlp92b3no9A3aUObQGIltvEEYQDKt
CobSmiLRSx0FK/pGYrYZilJlWStJLHySvnpbEkVDJGVL9Ua42Jn/VMXfBksRz01P
53wFmW7RAj8yyzDKA8P7rTjoJdypBRJZXphk+svceGOKv8Bxrcx3xgyF82Cl8YPk
Kl2YChCpbLewc+zxmRCz
=ShKh
-END PGP SIGNATURE-
___
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
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: Some NFS server V4 questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/25/14 09:58, Beeblebrox wrote: 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? I have vfs.nfsd.server_min_nfsvers=4 set on the server, and when I mount_nfs -o nfsv3 on the client, the error the client sees is [tcp] terp:/packages: NFSPROC_NULL: RPC: Program/version mismatch; low version = 4, high version = 4 Have to ^C to exit. Nothing shows up in the server's log, but because of sloth I haven't tried to make anything show up. Maybe there's an option. Best, Russell -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJUTAhKAAoJEFnLrGVSDFaEctoP/3VAFxrLfkYDPTsKrCMD0pJf RrNY0ePTVueDltsVXeEpT/pxSzN7RKLhWL0AB0IsoTWBvZZCHTbwv7GvF0yufxNW +oU29DEceIc8dxhXqjjOCKM3Na85C90idukemDG5ZaZoDU9d//POKaV1ET5HwQNq mZ1q4pqNjnf/O0q+7KjOxVvOnA1g7T2x/HxvL7D0RbmO6EGoRNXbMzxidQmcRDSG V4pmS5GoTUuOqTeXqYbrHJsF8tBaxKqcsOcz90LIWoilYCxiVccPY9SI+EYhX0hq ExVzTvt5OvfNSmz252m8I+87Sw0KA9r06fTpbARuK9Afyt/KNcOU/vANjzDegzLG 8u9TcnBfsqNR7K3pqyvt4jyVW6fliI79i1wpVw2ZNn02vGSn1l2iHWzddX9y0Hmj l1VMM2nWgag8V7wHebRmxILZMHK+VU4gWxp4hTXm0GkXHV27vPWY7eMQtbz/e7yu OpqPSUO7AEp6PTMCZoQY8uIEqmfJIKnyv2/ua3RgNtqM1srvjg1nugxXjfD8z9m6 PH0EY691Rv5hUScXwRtcElO8pziKWFbiXE1HrpPDMnpTtq6Wg5r/ubwepWTrmNJC FfdNOzTCVSF6nBMAo7pwV2P2ATHQkDQjMJJ7B8jZPOapCX59q2Cgth/jX0muiX3g wKbO2ZvSZa7lDAmBcecj =DKjs -END PGP SIGNATURE- ___ 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
junior kernel tasks
Hello, In short, nice kernel tasks people with C language skills can do in few evenings. https://wiki.freebsd.org/JuniorJobs It is assumed you know how to obtain sources and build the kernel. What you can get in return: - your own code in FreeBSD tree - eternal glory [1] - fun [2] If you are not interested, but know someone who does, please pass it down. [1] - not really, no [2] - well, I guess that's subjective, so that's not a no Cheers, -- Mateusz Guzik mjguzik gmail.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: Ver 2 of the patch [was: Re: i915 driver update testing]
Hi, I can confirm v6 of the patch works for me with a r273559 kernel on a i5-3320M notebook as well. Only interesting new output to messages: Oct 25 23:11:19 kernel: error: [drm:pid1159:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 0007, was 1807 Oct 25 23:11:28 kernel: error: [drm:pid1159:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 1807, was Oct 25 23:11:36 kernel: error: [drm:pid1159:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 1807, was 1800 Oct 25 23:11:48 kernel: error: [drm:pid1159:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 1807, was 1800 Thanks a lot! Johannes On Thu, Oct 23, 2014 at 9:03 PM, Konstantin Belousov kostik...@gmail.com wrote: On Wed, Oct 22, 2014 at 03:59:23PM -0400, Adam McDougall wrote: On 10/22/2014 08:26, Konstantin Belousov wrote: On Wed, Oct 08, 2014 at 03:12:08PM -0400, Adam McDougall wrote: On 10/08/2014 13:05, Konstantin Belousov wrote: There are more occurences of the bug I fixed once in patch version 2. Also, since pmap changes were committed in modified form, please try the updated patch at https://www.kib.kiev.ua/kib/drm/i915.3.patch . No apparent change: http://www.egr.msu.edu/~mcdouga9/i915-patch3-1.txt cite (kgdb) p *(struct drm_i915_private *)(dev_private) cite No symbol dev_private in current context. This is p *(struct drm_i915_private *)(dev-dev_private) http://www.egr.msu.edu/~mcdouga9/dev_private.txt I regenerated patch after recent merges and changes in KPI on HEAD. https://www.kib.kiev.ua/kib/drm/i915.4.patch Please apply it, I think the issue should be there still. Then apply the following debugging patch, and set kenv drm.debug=0x3 before loading i915kms.ko. I want to see the same debugging information, and dmesg from the moment of loading the driver. In fact, try https://www.kib.kiev.ua/kib/drm/i915.5.patch Due to my mistake during the patch generation, i915.5.patch is just a garbage. Use https://www.kib.kiev.ua/kib/drm/i915.6.patch. I already have one private report of the patch worked from person who got the same panic in iicbb. ___ 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: Some NFS server V4 questions
Beeblebrox wrote:
* I can't get the NFS server to run V4 only. I have:
sysctl vfs.nfsd.server_min_nfsvers=4
Hmm. With this set the NFS server shouldn't accept V2, 3
RPCs. The mount will work, since that is done by the Mount
protocol (mountd), but the client should be saying server
not responding... whenever it tries to access the V2, 3
mounts. Not sure why NFSv3 is still working after this is set.
I'll try a quick test of it here.
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)?
I am not aware of any plans to drop V2/V3. Although V2 isn't used much
any more V3 will be around for a long time to come, imho. (I'll probably
be long gone before V3 is.)
The new client and server support V2, 3 and 4. (Maybe it was the talk
about getting rid of the oldnfs stuff that made you think V2, 3 were
going away?
rick
* 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
___
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
Russell L. Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/25/14 03:07, Beeblebrox wrote:
* I can't get the NFS server to run V4 only. I have: sysctl
vfs.nfsd.server_min_nfsvers=4
[...]
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
Possibly need to arrange for mount_nfs to see -o nfsv4
(I use mount_nfs -o nfsv4,minorversion=1)
Then nfsstat shows eg:
terp:/library on /mnt/terp/library
nfsv4,minorversion=1,tcp,resvport,hard,cto,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=65536,wsize=65536,readdirsize=65536,readahead=1,wcommitsize=2798255,timeout=120,retrans=2147483647
HTH,
Russell
* 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)?
As noted in the other reply, I am not aware of any plan to get rid
of NFSv2 or v3 and would oppose any such plan.
rick
* 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
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBAgAGBQJUS8a3AAoJEFnLrGVSDFaEvWEP/iIKgw1kTmGQqgYAzVY++8uq
X3XMSnUFNGkyZSO/cz9gCO8S+oXkWVD8z3UbTKtyPCdTHhp48klTRW+ceSGvfhq2
oyWfcM5bXbOBLQZaoz66IL77mZHlWOTOLoGyNQZp7x/7KXETN7nK+qxQ1WDD7WM9
BW8fC+krQ4F5Tvqc70fylu93QKKUiqi26cOMWuRLTwgLXJY+NtPLMjH+SadDonNC
FvszjFpTsoP7cKPWA0vPA2iLb3Q43DT1+k23r6iY33JzTX2LW+zpzk+i4wEneNE8
JAgGqsFB08sH8krBrKo3n5+zcd5R0mZu3uX9a0CQJYiNHg6Phh4QgyETTYJT0ig/
mF1Q7V5z4FHLKdZigqO2WjNN2l2zfzDlUWfDTyc/b8CZIaPJemdqADsBVl76UdX8
2HspYZdAxR2zPc9EmpNPQJAksBFyUpwZy6cpHW+7wrkeeYoTWZLYV5sm4IscOzEE
tdof9VRIT+DGPrxLPFxO8tQiOV0eQWh3Om7Tlp92b3no9A3aUObQGIltvEEYQDKt
CobSmiLRSx0FK/pGYrYZilJlWStJLHySvnpbEkVDJGVL9Ua42Jn/VMXfBksRz01P
53wFmW7RAj8yyzDKA8P7rTjoJdypBRJZXphk+svceGOKv8Bxrcx3xgyF82Cl8YPk
Kl2YChCpbLewc+zxmRCz
=ShKh
-END PGP SIGNATURE-
___
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: Some NFS server V4 questions
Russell L. Carter wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/25/14 09:58, Beeblebrox wrote: 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? I have vfs.nfsd.server_min_nfsvers=4 set on the server, and when I mount_nfs -o nfsv3 on the client, the error the client sees is [tcp] terp:/packages: NFSPROC_NULL: RPC: Program/version mismatch; low version = 4, high version = 4 Have to ^C to exit. Nothing shows up in the server's log, but because of sloth I haven't tried to make anything show up. Maybe there's an option. There isn't an option to log the attempts, but it does seem to have disallowed NFSv3 RPCs. rick Best, Russell -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJUTAhKAAoJEFnLrGVSDFaEctoP/3VAFxrLfkYDPTsKrCMD0pJf RrNY0ePTVueDltsVXeEpT/pxSzN7RKLhWL0AB0IsoTWBvZZCHTbwv7GvF0yufxNW +oU29DEceIc8dxhXqjjOCKM3Na85C90idukemDG5ZaZoDU9d//POKaV1ET5HwQNq mZ1q4pqNjnf/O0q+7KjOxVvOnA1g7T2x/HxvL7D0RbmO6EGoRNXbMzxidQmcRDSG V4pmS5GoTUuOqTeXqYbrHJsF8tBaxKqcsOcz90LIWoilYCxiVccPY9SI+EYhX0hq ExVzTvt5OvfNSmz252m8I+87Sw0KA9r06fTpbARuK9Afyt/KNcOU/vANjzDegzLG 8u9TcnBfsqNR7K3pqyvt4jyVW6fliI79i1wpVw2ZNn02vGSn1l2iHWzddX9y0Hmj l1VMM2nWgag8V7wHebRmxILZMHK+VU4gWxp4hTXm0GkXHV27vPWY7eMQtbz/e7yu OpqPSUO7AEp6PTMCZoQY8uIEqmfJIKnyv2/ua3RgNtqM1srvjg1nugxXjfD8z9m6 PH0EY691Rv5hUScXwRtcElO8pziKWFbiXE1HrpPDMnpTtq6Wg5r/ubwepWTrmNJC FfdNOzTCVSF6nBMAo7pwV2P2ATHQkDQjMJJ7B8jZPOapCX59q2Cgth/jX0muiX3g wKbO2ZvSZa7lDAmBcecj =DKjs -END PGP SIGNATURE- ___ 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: RFC: getting rid of oldnfs
Kostik wrote: On Fri, Oct 24, 2014 at 04:43:28PM +0100, Robert Watson wrote: On Thu, 23 Oct 2014, Rick Macklem wrote: Someone just pinged me on this and I figured I should bring it up. 1 - Is anyone out there still using oldnfs due to unresolved problems with the new one? (I am not aware of any outstanding issues in the new nfs that don't exist in the oldnfs.) 2 - Does anyone see a problem with getting rid of oldnfs for FreebSD-11? 3 - If I get rid of it in -head, I can do it either in mid-December or mid-April. (I can't do commits during the winter.) Does anyone have a rough idea when the 11.0 release cycle will start, so I can choose which of the above would be preferable? (I figured I'd wait until after the last 10.n release that happens before 11.0, since it will be easier to MFC before the removal of oldnfs.) Thanks in advance for any comments, rick ps: John, I've cc'd you since I thought you are the guy most likely to need to do commits/MFCs to oldnfs. I think removing it is fine, but as early as possible (as John says) to give our -CURRENT users time to stop working around bugs and start reporting them :-). I remember the main reason for keeping oldnfs, both server and client, around in HEAD was to facilitate MFC of fixes to the branches which still use oldnfs, i.e. stable/8. If this reason is still valid, oldnfs have to stay in HEAD till stable/8 is supported or interested for developers. I usually do not like direct commits into the stable branches. Otherwise, I see no reason to keep oldnfs around. Well, the only commits I've done to old were bugfixes that applied to both old and new. John has been the main fix the old NFS guy lately. So, John, do you anticipate more patches to the old NFS that need to be MFC'd down? Thanks, rick ___ 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
buildkernel fails on head
I'm trying to build the current FreeBSD kernel, and that's what I get: % sudo make buildkernel -- Kernel build for GENERIC started on Sun Oct 26 01:39:13 MSK 2014 -- === GENERIC mkdir -p /usr/obj/usr/src/head/sys -- stage 1: configuring the kernel -- cd /usr/src/head/sys/amd64/conf; PATH=/usr/obj/usr/src/head/tmp/legacy/usr/sbin:/usr/obj/usr/src/head/tmp/legacy/usr/bin:/usr/obj/usr/src/head/tmp/legacy/usr/games:/usr/obj/usr/src/head/tmp/legacy/bin:/usr/obj/usr/src/head/tmp/usr/sbin:/usr/obj/usr/src/head/tmp/usr/bin:/usr/obj/usr/src/head/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /usr/obj/usr/src/head/sys/GENERIC -I '/usr/src/head/sys/amd64/conf' '/usr/src/head/sys/amd64/conf/GENERIC' config: illegal option -- I usage: config [-CgmpV] [-d destdir] sysname config -x kernel *** Error code 64 Stop. make[1]: stopped in /usr/src/head *** Error code 1 Stop. make: stopped in /usr/src/head is there a workaround for that? Is the kernel build broken? -- wbr, Maxim Filimonov c...@bein.link ___ 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
Russell L. Carter wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/25/14 09:58, Beeblebrox wrote: 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? I have vfs.nfsd.server_min_nfsvers=4 set on the server, and when I mount_nfs -o nfsv3 on the client, the error the client sees is [tcp] terp:/packages: NFSPROC_NULL: RPC: Program/version mismatch; low version = 4, high version = 4 Have to ^C to exit. I just did a quick test. 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.) rick Nothing shows up in the server's log, but because of sloth I haven't tried to make anything show up. Maybe there's an option. Best, Russell -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJUTAhKAAoJEFnLrGVSDFaEctoP/3VAFxrLfkYDPTsKrCMD0pJf RrNY0ePTVueDltsVXeEpT/pxSzN7RKLhWL0AB0IsoTWBvZZCHTbwv7GvF0yufxNW +oU29DEceIc8dxhXqjjOCKM3Na85C90idukemDG5ZaZoDU9d//POKaV1ET5HwQNq mZ1q4pqNjnf/O0q+7KjOxVvOnA1g7T2x/HxvL7D0RbmO6EGoRNXbMzxidQmcRDSG V4pmS5GoTUuOqTeXqYbrHJsF8tBaxKqcsOcz90LIWoilYCxiVccPY9SI+EYhX0hq ExVzTvt5OvfNSmz252m8I+87Sw0KA9r06fTpbARuK9Afyt/KNcOU/vANjzDegzLG 8u9TcnBfsqNR7K3pqyvt4jyVW6fliI79i1wpVw2ZNn02vGSn1l2iHWzddX9y0Hmj l1VMM2nWgag8V7wHebRmxILZMHK+VU4gWxp4hTXm0GkXHV27vPWY7eMQtbz/e7yu OpqPSUO7AEp6PTMCZoQY8uIEqmfJIKnyv2/ua3RgNtqM1srvjg1nugxXjfD8z9m6 PH0EY691Rv5hUScXwRtcElO8pziKWFbiXE1HrpPDMnpTtq6Wg5r/ubwepWTrmNJC FfdNOzTCVSF6nBMAo7pwV2P2ATHQkDQjMJJ7B8jZPOapCX59q2Cgth/jX0muiX3g wKbO2ZvSZa7lDAmBcecj =DKjs -END PGP SIGNATURE- ___ 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: HEADS UP: Merging projects/bhyve_svm to HEAD
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: HEADS UP: Merging projects/bhyve_svm to HEAD
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
