Re: Working on Zoom port

[Alexandr Krivulya]

13.04.20 19:59, Жилин, Михаил Сергеевич пишет:

Hi,

Does the latest Firefox support audio in Zoom? It's really the only 
pain point of Firefox + Zoom on FreeBSD.
I'm forced to use it every day, so Web client is cool except for audio 
issue on Firefox.




According to [1] latest firefox nightly builds now support audio in 
zoom. This nightly builds are not available for FreeBSD but you can try 
to build it from sources.


[1] 
https://www.reddit.com/r/firefox/comments/fsz3rk/implementation_of_the_audioworklets_makes_firefox/

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

Re: Working on Zoom port

[Alexandr Krivulya]

13.04.20 17:38, Matthias Apitz пишет:

El día lunes, abril 13, 2020 a las 09:06:06a. m. +0300, Alexandr Krivulya 
escribió:


13.04.20 04:58, Rodney W. Grimes пишет:

All,

Given how Zoom is getting used a lot more these days, I've started
working on a port that installs the Zoom linux client.

Here is a link to my github if anyone wants to help:

https://github.com/emc2/freebsd-ports/tree/zoom


I'm not done yet.  The zoom linux client installs a bunch of Qt
libraries in its own directory.  These either need to be installed with
a port, or else the right configs need to be set to search for libraries
there.

I'm going to take a break, but I'm going to circle back to this.


You are aware of the rather large pile of recent security issues
surronding zoom I hope.

Yes, you right. But a lot of people (as me) use it for non-confidential
or educational purposes. So working zoom client is very important for me
for example.
I'm not a developer, but can test your port, Eric. Thank you!

Hello,

Please, can some kind soul enlighten me a bit how this (zooom.us) works
from a technical point of view. The background of my question, and I've
never used zoom before, is that my son receives via mail MS OutLook
invitations (due to the closing of his misuc shool for Corona virus) and
if I open them on my Windows business laptop, it downloads
for every new session some piece(s) of software, which is then executed
and establishes an audio/video session with his teacher.

How this works exactly a how this is supposed to work on FreeBSD?

Thanks

matthias


Hello!
All of you need - a conference ID and probably password. Now you can 
participate in conference by pressing Join button in zoom client and 
providing this ID and/or password. Conference ID is part of your url 
after '/j/' - for example conference url is 
https://zoom.us/j/111222333?pwd=ejhxhshyocdyaszT9 and conference ID is 
111222333. BTW, you can join conference via web-client from browser by 
url https://zoom.us/wc/join/YOUR-CONFERENCE-ID, but with firefox prior 
version 77 (nightly) without audio and with chromium without webcam 
(FreeBSD only, also audio and screen sharing works).


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

Re: Working on Zoom port

[Alexandr Krivulya]

13.04.20 04:58, Rodney W. Grimes пишет:

All,

Given how Zoom is getting used a lot more these days, I've started
working on a port that installs the Zoom linux client.

Here is a link to my github if anyone wants to help:

https://github.com/emc2/freebsd-ports/tree/zoom


I'm not done yet.  The zoom linux client installs a bunch of Qt
libraries in its own directory.  These either need to be installed with
a port, or else the right configs need to be set to search for libraries
there.

I'm going to take a break, but I'm going to circle back to this.


You are aware of the rather large pile of recent security issues
surronding zoom I hope.


Yes, you right. But a lot of people (as me) use it for non-confidential 
or educational purposes. So working zoom client is very important for me 
for example.

I'm not a developer, but can test your port, Eric. Thank you!
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Firefox and Cliqz tabs crashing at GOV.UK government pages

[Alexandr Krivulya]

11.04.20 03:34, Graham Perrin пишет:

On 08/04/2020 20:23, Graham Perrin wrote:

> Firefox 75.0_1,1 tabs crashing or mis-rendering at some www.gov.uk 
pages

>
> Most noticeable today at . 
Screenshots available on request.

>
> AFAICT the same types of problem with 75.0_1,1 on both r357746 and 
r359628.


The problem persists with r359750, is reproducible with a different 
user account, is reproducible with Cliqz browser. As far as I can 
tell, only bugging UK.GOV government pages.


Occasionally a page will appear OK (e.g. the screen to the left at 
), more often the page will appear 
wrong (screen to the right, safe mode).


Most often: the tab will crash before the screen can be read. Crashes 
seem to occur at load time, towards the tail end of content loading or 
rendering.




I can't reproduce it on my current (r359770, amd64, firefox-75.0_1,1), 
this page loads fine, no any mis-rendering or crashing.

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

Re: kernel build failed

[Alexandr Krivulya]

29.03.20 14:55, Dimitry Andric пишет:

On 29 Mar 2020, at 13:02, Alexandr Krivulya  wrote:

28.03.20 18:32, Dimitry Andric пишет:

On 28 Mar 2020, at 13:48, Alexandr Krivulya  wrote:

...

This typically happens if you don't run "make buildworld", or at least
"make kernel-toolchain" before running "make buildkernel", and your
userland is missing those headers, for some reason. (Usually people
seem to do a WITHOUT_CLANG installation or strip out 'unnecessary'
stuff manually...)


I have updated source tree to r359419 and now make builworld failed with an 
error:

--- Basic/Targets.o ---
c++  -O2 -pipe -I/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libclang 
-I/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libllvm 
-I/usr/src/contrib/llvm-project/clang/lib/Basic -I/usr/src/contrib/llvm-project/clang/lib/Driver 
-I/usr/src/contrib/llvm-project/clang/include -I/usr/src/lib/clang/include 
-I/usr/src/contrib/llvm-project/llvm/include -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS 
-D__STDC_LIMIT_MACROS -DHAVE_VCS_VERSION_INC 
-DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd13.0\" 
-DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd13.0\" 
-DDEFAULT_SYSROOT=\"/usr/obj/usr/src/amd64.amd64/tmp\" -DLLVM_TARGET_ENABLE_X86 
-DLLVM_NATIVE_ASMPARSER=LLVMInitializeX86AsmParser -DLLVM_NATIVE_ASMPRINTER=LLVMInitializeX86AsmPrinter 
-DLLVM_NATIVE_DISASSEMBLER=LLVMInitializeX86Disassembler -DLLVM_NATIVE_TARGET=LLVMInitializeX86Target 
-DLLVM_NATIVE_TARGETINFO=LLVMInitializeX86TargetInfo -DLLVM_NATIVE_TARGETMC=LLVMInitializeX86TargetMC 
-ffunction-sections -fdata-sections -gline-tables-only -MD -MF.depend.Basic_Targets.o -MTBasic/Targets.o 
-Wno-format-zero-length -Qunused-arguments -include ../freebsd_cc_version.h 
-I/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include -fno-exceptions -fno-rtti -gline-tables-only -std=c++14 
-stdlib=libc++ -Wno-c++11-extensions   -c /usr/src/contrib/llvm-project/clang/lib/Basic/Targets.cpp -o 
Basic/Targets.o
--- Basic/SourceManager.o ---
/usr/src/contrib/llvm-project/clang/lib/Basic/SourceManager.cpp:1228:10: fatal 
error: 'emmintrin.h' file not found
#include 
  ^

If this happens during the cross-tools stage (stage 3), then your base
system's toolchain is missing some components.  Can you check whether
the directory /usr/lib/clang/x.y.z exists, where x.y.z is the version
printed by "cc -v" ?

If that directory does not exist, the easiest fix is probably to use
a toolchain port to bootstrap, or alternatively restore the toolchain
directories from a 13-CURRENT snapshot.




You are absolutely right. The directory /usr/lib/clang was empty.
Thank you!

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

Re: kernel build failed

[Alexandr Krivulya]

29.03.20 14:12, David Wolfskill пишет:

On Sun, Mar 29, 2020 at 02:02:02PM +0300, Alexandr Krivulya wrote:

28.03.20 18:32, Dimitry Andric пишет:
...

This typically happens if you don't run "make buildworld", or at least
"make kernel-toolchain" before running "make buildkernel", and your
userland is missing those headers, for some reason. (Usually people
seem to do a WITHOUT_CLANG installation or strip out 'unnecessary'
stuff manually...)


I have updated source tree to r359419 and now make builworld failed with an
error:

...
--- Basic/SourceManager.o ---
/usr/src/contrib/llvm-project/clang/lib/Basic/SourceManager.cpp:1228:10:
fatal error: 'emmintrin.h' file not found
#include 
  ^
1 error generated.
*** [Basic/SourceManager.o] Error code 1


Perhaps it would be helpful for you specify precisely what commands you
invoked once the source tree was updated.

For example, the process I use is documented in
http://www.catwhisker.org/~david/FreeBSD/upgrade.html



Nothing specific, I use this scenario for years:

svnlite up /usr/src
rm -rf /usr/obj
cd /usr/src
make buildworld
make kernel
mergemaster -p
make installworld
mergemaster -Ui
reboot
make delete-old
make delete-old-libs


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

Re: kernel build failed

[Alexandr Krivulya]

28.03.20 18:32, Dimitry Andric пишет:

On 28 Mar 2020, at 13:48, Alexandr Krivulya  wrote:

28.03.20 14:35, David Wolfskill пишет:

On Sat, Mar 28, 2020 at 02:01:39PM +0200, Alexandr Krivulya wrote:

Hello,
on latest CURRENT kernel fails to build:

===> aesni (all)
[Creating objdir 
/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/modules/usr/src/sys/modules/aesni...]
...
/usr/src/sys/crypto/aesni/aesni_ghash.c:75:10: fatal error: 'wmmintrin.h'
file not found
#include 
  ^
1 error generated.
*** Error code 1


I had no issues updating from r359325 to r359356 yesterday, or from
r359356 to r359389 today (using META_MODE).

So what may be a reason? I tried:
- remove and checkout source tree
- remove /usr/obj

wmmintrin.h is present under 
/usr/src/contrib/llvm-project/clang/lib/Headers/wmmintrin.h

/etc/make.conf:
KERNCONF=GENERIC-NODEBUG
MALLOC_PRODUCTION=yes

no /etc/src.conf

This typically happens if you don't run "make buildworld", or at least
"make kernel-toolchain" before running "make buildkernel", and your
userland is missing those headers, for some reason. (Usually people
seem to do a WITHOUT_CLANG installation or strip out 'unnecessary'
stuff manually...)



I have updated source tree to r359419 and now make builworld failed with 
an error:


--- Basic/Targets.o ---
c++  -O2 -pipe 
-I/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libclang 
-I/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libllvm 
-I/usr/src/contrib/llvm-project/clang/lib/Basic 
-I/usr/src/contrib/llvm-project/clang/lib/Driver 
-I/usr/src/contrib/llvm-project/clang/include 
-I/usr/src/lib/clang/include 
-I/usr/src/contrib/llvm-project/llvm/include -D__STDC_CONSTANT_MACROS 
-D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -DHAVE_VCS_VERSION_INC 
-DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd13.0\" 
-DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd13.0\" 
-DDEFAULT_SYSROOT=\"/usr/obj/usr/src/amd64.amd64/tmp\" 
-DLLVM_TARGET_ENABLE_X86 
-DLLVM_NATIVE_ASMPARSER=LLVMInitializeX86AsmParser 
-DLLVM_NATIVE_ASMPRINTER=LLVMInitializeX86AsmPrinter 
-DLLVM_NATIVE_DISASSEMBLER=LLVMInitializeX86Disassembler 
-DLLVM_NATIVE_TARGET=LLVMInitializeX86Target 
-DLLVM_NATIVE_TARGETINFO=LLVMInitializeX86TargetInfo 
-DLLVM_NATIVE_TARGETMC=LLVMInitializeX86TargetMC -ffunction-sections 
-fdata-sections -gline-tables-only -MD -MF.depend.Basic_Targets.o 
-MTBasic/Targets.o -Wno-format-zero-length -Qunused-arguments -include 
../freebsd_cc_version.h 
-I/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include -fno-exceptions 
-fno-rtti -gline-tables-only -std=c++14 -stdlib=libc++ 
-Wno-c++11-extensions   -c 
/usr/src/contrib/llvm-project/clang/lib/Basic/Targets.cpp -o Basic/Targets.o

--- Basic/SourceManager.o ---
/usr/src/contrib/llvm-project/clang/lib/Basic/SourceManager.cpp:1228:10: 
fatal error: 'emmintrin.h' file not found

#include 
 ^
1 error generated.
*** [Basic/SourceManager.o] Error code 1

make[4]: stopped in /usr/src/lib/clang/libclang
1 error

make[4]: stopped in /usr/src/lib/clang/libclang
*** [all_subdir_lib/clang/libclang] Error code 2

make[3]: stopped in /usr/src/lib/clang
1 error

make[3]: stopped in /usr/src/lib/clang
*** [cross-tools] Error code 2

make[2]: stopped in /usr/src
1 error

make[2]: stopped in /usr/src
*** [_cross-tools] Error code 2

make[1]: stopped in /usr/src
1 error

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

make: stopped in /usr/src
1 error

make: stopped in /usr/src

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

Re: kernel build failed

[Alexandr Krivulya]

28.03.20 14:35, David Wolfskill пишет:

On Sat, Mar 28, 2020 at 02:01:39PM +0200, Alexandr Krivulya wrote:

Hello,
on latest CURRENT kernel fails to build:

===> aesni (all)
[Creating objdir 
/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/modules/usr/src/sys/modules/aesni...]
...
/usr/src/sys/crypto/aesni/aesni_ghash.c:75:10: fatal error: 'wmmintrin.h'
file not found
#include 
  ^
1 error generated.
*** Error code 1


I had no issues updating from r359325 to r359356 yesterday, or from
r359356 to r359389 today (using META_MODE).


So what may be a reason? I tried:
- remove and checkout source tree
- remove /usr/obj

wmmintrin.h is present under 
/usr/src/contrib/llvm-project/clang/lib/Headers/wmmintrin.h


/etc/make.conf:
KERNCONF=GENERIC-NODEBUG
MALLOC_PRODUCTION=yes

no /etc/src.conf
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

kernel build failed

[Alexandr Krivulya]

Hello,
on latest CURRENT kernel fails to build:

===> aesni (all)
[Creating objdir 
/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/modules/usr/src/sys/modules/aesni...]

machine -> /usr/src/sys/amd64/include
x86 -> /usr/src/sys/x86/include
awk -f /usr/src/sys/tools/makeobjops.awk /usr/src/sys/kern/device_if.m -h
awk -f /usr/src/sys/tools/makeobjops.awk /usr/src/sys/kern/bus_if.m -h
ln -sf /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/opt_bus.h opt_bus.h
awk -f /usr/src/sys/tools/makeobjops.awk 
/usr/src/sys/opencrypto/cryptodev_if.m -h
cc -target x86_64-unknown-freebsd13.0 
--sysroot=/usr/obj/usr/src/amd64.amd64/tmp 
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -c -O2 -pipe 
-fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -DKLD_TIED -nostdinc 
-DHAVE_KERNEL_OPTION_HEADERS -include 
/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/opt_global.h -I. 
-I/usr/src/sys -I/usr/src/sys/contrib/ck/include -g 
-fno-omit-frame-pointer -mno-omit-leaf-frame-pointer 
-fdebug-prefix-map=./machine=/usr/src/sys/amd64/include 
-fdebug-prefix-map=./x86=/usr/src/sys/x86/include 
-I/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG -MD 
-MF.depend.genoffset.o -MTgenoffset.o -mcmodel=kernel -mno-red-zone 
-mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables 
-ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall 
-Wredundant-decls -Wnested-externs -Wstrict-prototypes 
-Wmissing-prototypes -Wpointer-arith -Wcast-qual -Wundef 
-Wno-pointer-sign -D__printf__=__freebsd_kprintf__ 
-Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas 
-Wno-error-tautological-compare -Wno-error-empty-body 
-Wno-error-parentheses-equality -Wno-error-unused-function 
-Wno-error-pointer-sign -Wno-error-shift-negative-value 
-Wno-address-of-packed-member -Wno-format-zero-length -mno-aes -mno-avx 
-std=iso9899:1999  /usr/src/sys/kern/genoffset.c

sh /usr/src/sys/kern/genoffset.sh genoffset.o > offset.inc
cc -target x86_64-unknown-freebsd13.0 
--sysroot=/usr/obj/usr/src/amd64.amd64/tmp 
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -c -O3 -pipe 
-fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -DKLD_TIED 
-DHAVE_KERNEL_OPTION_HEADERS -include 
/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/opt_global.h -I. 
-I/usr/src/sys -I/usr/src/sys/contrib/ck/include -fno-common -g 
-fno-omit-frame-pointer -mno-omit-leaf-frame-pointer 
-fdebug-prefix-map=./machine=/usr/src/sys/amd64/include 
-fdebug-prefix-map=./x86=/usr/src/sys/x86/include 
-I/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG -MD 
-MF.depend.aesni_ghash.o -MTaesni_ghash.o -mcmodel=kernel -mno-red-zone 
-mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables 
-ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall 
-Wredundant-decls -Wnested-externs -Wstrict-prototypes 
-Wmissing-prototypes -Wpointer-arith -Wcast-qual -Wundef 
-Wno-pointer-sign -D__printf__=__freebsd_kprintf__ 
-Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas 
-Wno-error-tautological-compare -Wno-error-empty-body 
-Wno-error-parentheses-equality -Wno-error-unused-function 
-Wno-error-pointer-sign -Wno-error-shift-negative-value 
-Wno-address-of-packed-member -Wno-format-zero-length 
-Wno-error-cast-qual -mno-aes -mno-avx -std=iso9899:1999 -Werror -mmmx 
-msse -msse4 -maes -mpclmul /usr/src/sys/crypto/aesni/aesni_ghash.c
/usr/src/sys/crypto/aesni/aesni_ghash.c:75:10: fatal error: 
'wmmintrin.h' file not found

#include 
 ^
1 error generated.
*** Error code 1

Stop.
make[4]: stopped in /usr/src/sys/modules/aesni
*** Error code 1

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

Stop.
make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
*** Error code 1

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

Stop.
make: stopped in /usr/src
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ipsec not working

[Alexandr Krivulya]

Ok, thank you.

12.05.19 09:35, Kubilay Kocak пишет:

On 12/05/2019 4:20 pm, Alexandr Krivulya wrote:

Hi,
after upgrading from r347050 to r347483 ipsec tunel on my notebook 
does not work any more. Connection is established as usual but no 
policies are installed.


2019-05-12 09:12:10 00[DMN] Starting IKE charon daemon (strongSwan 
5.7.2, FreeBSD 13.0-CURRENT, amd64)
2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: 
Protocol not available

2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed
2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: 
Protocol not available

2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed
2019-05-12 09:12:10 00[KNL] unable to set UDP_ENCAP: Invalid argument
2019-05-12 09:12:10 00[NET] enabling UDP decapsulation for IPv6 on 
port 4500 failed
2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: 
Protocol not available

2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed
2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: 
Protocol not available

2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed
2019-05-12 09:12:10 00[KNL] unable to set UDP_ENCAP: Protocol not 
available
2019-05-12 09:12:10 00[NET] enabling UDP decapsulation for IPv4 on 
port 4500 failed


...

2019-05-12 09:12:10 01[CFG]  selected proposal: 
ESP:AES_CBC_256/HMAC_SHA2_256_128/NO_EXT_SEQ
2019-05-12 09:12:10 01[KNL]  unable to add SAD entry 
with SPI c96b2b97: Invalid argument (22)
2019-05-12 09:12:10 01[KNL]  unable to add SAD entry 
with SPI cc951335: Invalid argument (22)
2019-05-12 09:12:10 01[IKE]  unable to install 
inbound and outbound IPsec SA (SAD) in kernel
2019-05-12 09:12:10 01[IKE]  failed to establish 
CHILD_SA, keeping IKE_SA


See:

https://svnweb.freebsd.org/changeset/base/347410

Ongoing thread:

https://lists.freebsd.org/pipermail/svn-src-head/2019-May/124878.html



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

ipsec not working

[Alexandr Krivulya]

Hi,
after upgrading from r347050 to r347483 ipsec tunel on my notebook does 
not work any more. Connection is established as usual but no policies 
are installed.


2019-05-12 09:12:10 00[DMN] Starting IKE charon daemon (strongSwan 
5.7.2, FreeBSD 13.0-CURRENT, amd64)
2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: 
Protocol not available

2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed
2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: 
Protocol not available

2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed
2019-05-12 09:12:10 00[KNL] unable to set UDP_ENCAP: Invalid argument
2019-05-12 09:12:10 00[NET] enabling UDP decapsulation for IPv6 on port 
4500 failed
2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: 
Protocol not available

2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed
2019-05-12 09:12:10 00[KNL] unable to set IPSEC_POLICY on socket: 
Protocol not available

2019-05-12 09:12:10 00[NET] installing IKE bypass policy failed
2019-05-12 09:12:10 00[KNL] unable to set UDP_ENCAP: Protocol not available
2019-05-12 09:12:10 00[NET] enabling UDP decapsulation for IPv4 on port 
4500 failed


...

2019-05-12 09:12:10 01[CFG]  selected proposal: 
ESP:AES_CBC_256/HMAC_SHA2_256_128/NO_EXT_SEQ
2019-05-12 09:12:10 01[KNL]  unable to add SAD entry 
with SPI c96b2b97: Invalid argument (22)
2019-05-12 09:12:10 01[KNL]  unable to add SAD entry 
with SPI cc951335: Invalid argument (22)
2019-05-12 09:12:10 01[IKE]  unable to install inbound 
and outbound IPsec SA (SAD) in kernel
2019-05-12 09:12:10 01[IKE]  failed to establish 
CHILD_SA, keeping IKE_SA

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

Re: inetd startup script missing from /etc/rc.d in both -current and 11-stable

[Alexandr Krivulya]

Hi! I think you loose it after some updates. Both 11-stable and current 
contains it:


https://svnweb.freebsd.org/base/head/etc/rc.d/inetd?view=log
https://svnweb.freebsd.org/base/stable/11/etc/rc.d/inetd?view=log

Check your src tree and install it.

03.04.2017 17:00, tech-lists пишет:

Hello current@,

 From https://www.freebsd.org/doc/handbook/network-inetd.html I should be
able to start inetd like this:

service inetd start

...after enabling it in /etc/rc.conf. The inetd options look like this:

inetd_enable="YES"
inetd_program="/usr/sbin/inetd"
inetd_flags="-wW -C 60"

The problem is that the startup script doesn't exist in /etc/rc.d. I get
this error:

# service inetd start
inetd does not exist in /etc/rc.d or the local startup
directories (/usr/local/etc/rc.d), or is not executable

and the lines in rc.conf have no effect (inetd doesn't start).

I can, however, start it manually, as root, like this:

# inetd -wW -C 60

and it runs as expected.

This problem exists in 11-stable as well as -current. How can I fix this
please?

thanks,



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

Re: dchlient does not autostart anymore?

[Alexandr Krivulya]

+1
Need to manualy kldload ums.ko and start dhclient.

24.03.2017 12:38, Lev Serebryakov пишет:

On 24.03.2017 12:28, M - Krasznai András wrote:

  devd problems? Now dhclient and moused are started by devd.


Hi,

FreeBSD-current, r315895 also experiences the same problem. The problem started 
after updating my laptop yesterday morning. I can get an IP address after 
manually starting dhclient.

I have an additional anomaly: the USB mouse does not work (touchpad works) on a 
Lenovo T510 laptop. dmesg shows the correct vendor and type for the mouse.

rgds

András Krasznai



-Eredeti üzenet-
Feladó: owner-freebsd-curr...@freebsd.org 
[mailto:owner-freebsd-curr...@freebsd.org] Meghatalmazó Mark Millard
Küldve: 2017. március 24. 9:57
Címzett: zakharov...@gmail.com; FreeBSD Current
Tárgy: Re: dchlient does not autostart anymore?

Vladimir Zakharov zakharov.vv at gmail.com  wrote on Fri Mar 24 08:20:34 UTC 
2017:


After upgrading from r315544 to r315880 network interface doesn't get
IP address using DHCP on boot anymore.

$ grep re0 /etc/rc.conf | grep -v "^#"
ifconfig_re0="DHCP"

"service netif restart" doesn't help either. Only manual dhclient
starting.

I have just updated two contexts to -r315870 just a bit ago and they both got 
that behavior as well:

A) An amd64 context (FreeBSD client in VirtualBox under macOS)
B) An arm64 context (pine64+ 2GB with -mcpu=cortex-a53 )

Later I'll be updating powerpc64, powerpc, and armv6 (with
-mcpu=cortex-a7 ) contexts but I'd expect they will all match the behavior.

(I started from earlier than -r315544 so your report provides a better lower 
bound -r315544. I ended earlier and so my report provides a better upper bound 
-r315870.)

===
Mark Millard
markmi at dsl-only.net

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






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

Re: [RFC/RFT] projects/ipsec

[Alexandr Krivulya]

11.12.2016 01:07, Andrey V. Elsukov пишет:

Hi All,

I am pleased to announce that projects/ipsec, that I started several
months ago is ready for testing and review.
The main goals were:
   * rework locking to make IPsec code more friendly for concurrent
 processing;
   * make lookup in SADB/SPDB faster;
   * revise PFKEY implementation, remove stale code, make it closer
 to RFC;
   * implement IPsec VTI (virtual tunneling interface);
   * make IPsec code loadable as kernel module.

Currently all, except the last one is mostly done. So, I decided ask for
a help to test the what already done, while I will work on the last task.

How to try? There are no patches, you need to checkout the full
projects/ipsec source tree, and build the kernel and the base system.
There are very few changes in the base system, mostly the kernel
changes. Thus for testing that old configuration is still work, it is
enough to build only the kernel.

The approximate list of changes that may be visible to users:
* SA bundles now can have only 4 items in the chain. I think it is
enough, I can't imagine configurations when needed more. Also now SA
bundles supported for IPv6 too.
* due to changes in SPDB/SADB, systems where large number of SPs and SAs
are in use should get significant performance benefits.
* the memory consumption should slightly increase. There are several
hash tables and SP cache appeared.
* INPCB SP cache should noticeable increase network performance of
application when security policies are presence.
   https://lists.freebsd.org/pipermail/freebsd-net/2015-April/042121.html
* use transport mode IPsec for forwarded IPv4 packets now unsupported.
This matches the IPv6 behavior, and since we can handle the replies, I
think it is useless.
* Added net.inet.ipsec.check_policy_history sysctl variable. When it is
set, each inbound packet that was handled by IPsec will be checked
according to matching security policy. If not all IPsec transforms were
applied, the check will fail, and packet will be dropped.
* Many PF_KEY messages handlers was updated, probably some IKEd now may
fail due to stricter checks.
* SPI now unique for each SA. This also can break something.
* Added if_ipsec interface. For more info look at
   https://svnweb.freebsd.org/base?view=revision=309115
   https://reviews.freebsd.org/P112
* TCP_SIGNATURE code was reworked and now it behaves closer to RFC
   https://svnweb.freebsd.org/base?view=revision=309610
* NAT-T support was reworked.
   https://svnweb.freebsd.org/base?view=revision=309808
Also I made the patch to racoon that adds better support of NAT-T,
you can use this port to build patched racoon:
   https://people.freebsd.org/~ae/ipsec-tools.tgz

What results is interesting to me?
If you have some nontrivial configuration, please test.
If you have some configuration, that did't work, please test this branch.
If you have performance problems, please test. But don't forget that
this is head/ branch, you need to disable all debugging first.
If you just want to test, pay attention to the output of
`vmstat -m | egrep "sec|sah|pol|crypt"`.
If you have used TCP_SIGNATURE, IPSEC_NAT_T options, please test, this
support was significantly changed.

PS. I just updated the branch to last head/, and it was not tested, sorry :)



Hi, nothing unusual, all works fine. Strangswan in tunnel mode on current:

root@thinkpad:/home/shurik # ipsec status
Security Associations (1 up, 0 connecting):
ikev2-client[1]: ESTABLISHED 3 minutes ago, 
10.1.1.183[xxx..org.ua]...xxx.yyy.74.7[xxx..org.ua]
ikev2-client{1}:  INSTALLED, TUNNEL, reqid 1, ESP in UDP SPIs: 
c6f68157_i c6d17c85_o

ikev2-client{1}:   10.10.10.2/32 === 0.0.0.0/0

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

Re: ACPI Error on HP ProBook 430 G2

[Alexandr Krivulya]

03.01.2017 20:21, Jung-uk Kim пишет:

On 01/03/2017 11:22, Hans Petter Selasky wrote:

On 01/03/17 16:26, Moore, Robert wrote:

Not sure I understand. The fix has been committed, and is part of
version 20161222.



Hi Robert,

 From what I can see that patches have been pushed to the following
branch, vendor-sys/acpica/20161222/, see:

https://svnweb.freebsd.org/changeset/base/310451

But not yet to "master" (12-current) ?

Is that correct?

My console has been filling up with messages like this:


ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for
[OpcodeName unavailable] (20161117/dswexec-498)
ACPI Error: Method parse/execution failed
[\134_SB.PCI0.LPCB.H_EC._Q50] (Node 0xf800047fce40),
AE_AML_OPERAND_TYPE (20161117/psparse-560)
acpi_ec0: evaluation of query method _Q50 failed: AE_AML_OPERAND_TYPE

over the holidays, so I assume that means the previous version of ACPI,
20161117 which the 20161222 version is supposed to fix.

I was AFK for two weeks.  I will merge ACPICA 20161222 to FreeBSD head
this week when I find some free time.




I don't know if my problem related to this topic, but a few weeks I see 
in KDE battery capacity -1%. acpiconf shows no battery:


root@thinkpad:/home/shurik # acpiconf -i0
Design capacity:0 mWh
Last full capacity: 0 mWh
Technology: primary (non-rechargeable)
Design voltage: 0 mV
Capacity (warn):0 mWh
Capacity (low): 0 mWh
Low/warn granularity:   0 mWh
Warn/full granularity:  0 mWh
Model number:
Serial number:
Type:
OEM info:
State:  not present
Present voltage:12611 mV

Just updated to r311492 and problem still present. There is no such 
problem on previous kernel r310241. And there is no more error messages:


Jan  6 09:22:39 thinkpad kernel: ACPI Error: Needed type [Reference], 
found [Processor] 0xf800055d5000 (20161117/exresop-111)
Jan  6 09:22:39 thinkpad kernel: ACPI Error: Method parse/execution 
failed [\PNOT] (Node 0xf80005595bc0), AE_AML_OPERAND_TYPE 
(20161117/psparse-560)
Jan  6 09:22:39 thinkpad kernel: ACPI Error: Method parse/execution 
failed [\_SB.PCI0.LPCB.EC0._REG] (Node 0xf8000558a040), 
AE_AML_OPERAND_TYPE (20161117/psparse-560)



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

Re: ACPI Error on HP ProBook 430 G2

[Alexandr Krivulya]

21.12.2016 13:14, Edward Tomasz Napierała пишет:

On 1220T1734, O. Hartmann wrote:

Am Tue, 20 Dec 2016 18:09:20 +0300
Vladimir Zakharov  schrieb:


Hello!

Some time ago new ACPI messages appeared on console and in /var/log/messages. 
Like
these:

ACPI Error: Needed type [Reference], found [Processor] 0xf800043b8980
(20161117/exresop-111) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving 
operands
for [OpcodeName unavailable] (20161117/dswexec-498) ACPI Error: Method 
parse/execution
failed [\134_SB.PCI0.LPCB.EC0.PPNT] (Node 0xf80004396640), 
AE_AML_OPERAND_TYPE
(20161117/psparse-560) ACPI Error: Method parse/execution failed
[\134_SB.PCI0.LPCB.EC0._Q04] (Node 0xf80004396c40), AE_AML_OPERAND_TYPE
(20161117/psparse-560) acpi_ec0: evaluation of query method _Q04 failed:
AE_AML_OPERAND_TYPE

I'm sure that there were no such messages earlier. Suspend/resume works
for me. But after disconnecting power line hw.acpi.acline still equals
to 1. And powerd/powerdxx do not adjust CPU frequency anymore.

System info:
$ uname -a
FreeBSD vzakharov 12.0-CURRENT FreeBSD 12.0-CURRENT #14 r310326M: Tue Dec 20 
16:42:21
MSK 2016 root@vzakharov:/home/obj/usr/src/sys/GENERIC-NODEBUG  amd64

dmesg: http://pastebin.com/cYD8cR0b
hw.acpi: http://pastebin.com/Tht9B0FZ
acpidump: http://vzakharov.ru/z2v-HPProBook430G2.asl


PS. I'm not subscribed to freebsd-acpi. So keep me in CC, please.


I see lots of ACPI errors also shortly on a Lenovo E540 UEFI notebook running 
most recent
CURRENT ...

+1, I see the same on Thinkpad T420.
Same on Thinkpad E530, but hw.acpi.acline changes on ac lost and powerd 
works.


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

Re: Upgrading to r297291 LAGG(4) stops working.

[Alexandr Krivulya]

01.09.15 11:44, Gleb Smirnoff пишет:
> On Mon, Aug 31, 2015 at 09:58:45AM -0700, Adrian Chadd wrote:
> A> Hi,
> A> 
> A> +glebius, as he recently messed around with the wifi stack and his
> A> changes may have broken how mac addresses are assigned to the
> A> hardware.
>
> I've tested that with new code setting MAC address on wlan0 passed it
> down to device driver (iwn in my case).
>
> As Adrian already noted to Ranjan, his setup worked only by accident :)
> If it were not ath(4), but some more dumb WiFi device, the setup wouldn't
> work.
>

Hi,

On my -HEAD network traffic passes through re0 only when re0 is in
promisc mode. It was not required earlier. Is it necessary now?
My configuration is:

wlans_iwn0="wlan0"
ifconfig_wlan0="WPA country UA"
ifconfig_re0="ether 68:5d:43:92:3a:88 promisc"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto failover laggport re0 laggport wlan0  DHCP"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: IPSEC stop works after r285336

[Alexandr Krivulya]

29.07.2015 10:17, John-Mark Gurney пишет:
 Alexandr Krivulya wrote this message on Thu, Jul 23, 2015 at 10:38 +0300:

 [...]

 With r285535 all works fine.
 Sydney Meyer wrote this message on Mon, Jul 27, 2015 at 23:49 +0200:
 I'm having the same problem with IPSec, running -current with r285794.

 Don't know if this helps, but netstat -s -p esp shows packets dropped; bad 
 ilen.
 It looks like there was an issue w/ that commit...  After looking at
 the code, and working w/ gnn, I have committed r286000 which fixes it
 in my test cases...


Fixed for me. Thank you!
___
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: [CURRENT]: r285995: BROKEN! buildkernel fails in kern_shutdown.c

[Alexandr Krivulya]

29.07.2015 08:50, Conrad Meyer пишет:
 On Tue, Jul 28, 2015 at 10:21 PM, O. Hartmann
 ohart...@zedat.fu-berlin.de wrote:
 On Tue, 28 Jul 2015 21:58:26 -0700
 Conrad Meyer cse@gmail.com wrote:

 On Tue, Jul 28, 2015 at 9:35 PM, O. Hartmann
 ohart...@zedat.fu-berlin.de wrote:
 Sources as of r285995 fail to build kernel with

 [...]
 --- kernel ---
 linking kernel
 kern_shutdown.o: In function `kern_reboot':
 /usr/src/sys/kern/kern_shutdown.c:(.text+0x2e6): undefined reference to
 `bufshutdown' *** [kernel] Error code 1

 Hi,

 It appears you've got an old version of vfs_bio.o cached. Try deleting
 that and building.

 Best,
 Conrad
 I doubt that. When I start building world this morning, I deleted /usr/obj/*.
 So it should be not as you presumed.

 I just did a

 make -j12 kernel

 in /usr/src again and it failed at the very same position. Again, the source
 tree has been recently updated, afterwards I started buidlworld on a
 deleted/fresh /usr/obj.

 Well, r285993 is probably the offending commit. It looks ok to me,
 though I also hit:

 kern_shutdown.o: In function `kern_reboot':
 /usr/home/cmeyer/src/freebsd/sys/kern/kern_shutdown.c:315: undefined
 reference to `bufshutdown'


Fixed in r286002
___
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: IPSEC stop works after r285336

[Alexandr Krivulya]

27.07.2015 10:23, Alexandr Krivulya пишет:
 26.07.2015 21:39, George Neville-Neil пишет:

 On 25 Jul 2015, at 1:51, Alexandr Krivulya wrote:

 25.07.2015 00:38, John-Mark Gurney пишет:
 Alexandr Krivulya wrote this message on Thu, Jul 23, 2015 at 10:38
 +0300:
 I have IPSEC tunnel inside l2tp tunnel via mpd. After r285536 I see
 only
 outgoing esp packets on ng interface:
 This change is -stable, not -current, but the change referenced below
 is -current... Which one are you running?

 Also, the only ipsec related change after r285535 is r285770, though
 that probably won't effect it...  Could you possibly narrow the change
 that broke things?

 root@thinkpad:/usr/src # tcpdump -i ng0
 tcpdump: verbose output suppressed, use -v or -vv for full protocol
 decode
 listening on ng0, link-type NULL (BSD loopback), capture size
 262144 bytes
 10:35:27.331886 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9a5), length 140
 10:35:28.371707 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9a6), length 140
 10:35:29.443536 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9a7), length 140
 10:35:30.457370 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9a8), length 140
 10:35:31.475606 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9a9), length 140
 10:35:31.622315 IP 10.10.10.1.isakmp  10.10.10.2.isakmp: isakmp:
 phase
 2/others ? inf[E]
 10:35:31.622544 IP 10.10.10.2.isakmp  10.10.10.1.isakmp: isakmp:
 phase
 2/others ? inf[E]
 10:35:31.622658 IP 10.10.10.2.isakmp  10.10.10.1.isakmp: isakmp:
 phase
 2/others ? inf[E]
 10:35:31.623933 IP 10.10.10.1.isakmp  10.10.10.2.isakmp: isakmp:
 phase
 2/others ? inf[E]
 10:35:32.492349 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9aa), length 140
 10:35:33.509346 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9ab), length 140
 10:35:34.527187 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9ac), length 140
 10:35:35.539600 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9ad), length 140

 With r285535 all works fine.

 Right commit is in subject - r285336.
 There were two IPsec related commits after 285336.

 Either 285347 or 285526 could be the fix.  If you're OK after those
 two commits then the system is in correct working order.
 I have 285833 on my laptop now (world+kernel full rebuild), but problem
 still exists.

With IPSEC_DEBUG enabled I have a lot of messages:

kernel: esp_output: skip 20 hlen 24 rlen 76 padding 4 alen 20 blksd 16
kernel: esp_output: skip 20 hlen 24 rlen 160 padding 16 alen 20 blksd 16
kernel: esp_output: skip 20 hlen 24 rlen 30 padding 2 alen 20 blksd 16
kernel: esp_output: skip 20 hlen 24 rlen 161 padding 15 alen 20 blksd 16

___
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: IPSEC stop works after r285336

[Alexandr Krivulya]

26.07.2015 21:39, George Neville-Neil пишет:


 On 25 Jul 2015, at 1:51, Alexandr Krivulya wrote:

 25.07.2015 00:38, John-Mark Gurney пишет:
 Alexandr Krivulya wrote this message on Thu, Jul 23, 2015 at 10:38
 +0300:
 I have IPSEC tunnel inside l2tp tunnel via mpd. After r285536 I see
 only
 outgoing esp packets on ng interface:
 This change is -stable, not -current, but the change referenced below
 is -current... Which one are you running?

 Also, the only ipsec related change after r285535 is r285770, though
 that probably won't effect it...  Could you possibly narrow the change
 that broke things?

 root@thinkpad:/usr/src # tcpdump -i ng0
 tcpdump: verbose output suppressed, use -v or -vv for full protocol
 decode
 listening on ng0, link-type NULL (BSD loopback), capture size
 262144 bytes
 10:35:27.331886 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9a5), length 140
 10:35:28.371707 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9a6), length 140
 10:35:29.443536 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9a7), length 140
 10:35:30.457370 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9a8), length 140
 10:35:31.475606 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9a9), length 140
 10:35:31.622315 IP 10.10.10.1.isakmp  10.10.10.2.isakmp: isakmp:
 phase
 2/others ? inf[E]
 10:35:31.622544 IP 10.10.10.2.isakmp  10.10.10.1.isakmp: isakmp:
 phase
 2/others ? inf[E]
 10:35:31.622658 IP 10.10.10.2.isakmp  10.10.10.1.isakmp: isakmp:
 phase
 2/others ? inf[E]
 10:35:31.623933 IP 10.10.10.1.isakmp  10.10.10.2.isakmp: isakmp:
 phase
 2/others ? inf[E]
 10:35:32.492349 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9aa), length 140
 10:35:33.509346 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9ab), length 140
 10:35:34.527187 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9ac), length 140
 10:35:35.539600 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9ad), length 140

 With r285535 all works fine.


 Right commit is in subject - r285336.

 There were two IPsec related commits after 285336.

 Either 285347 or 285526 could be the fix.  If you're OK after those
 two commits then the system is in correct working order.

I have 285833 on my laptop now (world+kernel full rebuild), but problem
still exists.
___
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: IPSEC stop works after r285336

[Alexandr Krivulya]

25.07.2015 00:38, John-Mark Gurney пишет:
 Alexandr Krivulya wrote this message on Thu, Jul 23, 2015 at 10:38 +0300:
 I have IPSEC tunnel inside l2tp tunnel via mpd. After r285536 I see only
 outgoing esp packets on ng interface:
 This change is -stable, not -current, but the change referenced below
 is -current... Which one are you running?

 Also, the only ipsec related change after r285535 is r285770, though
 that probably won't effect it...  Could you possibly narrow the change
 that broke things?

 root@thinkpad:/usr/src # tcpdump -i ng0
 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
 listening on ng0, link-type NULL (BSD loopback), capture size 262144 bytes
 10:35:27.331886 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9a5), length 140
 10:35:28.371707 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9a6), length 140
 10:35:29.443536 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9a7), length 140
 10:35:30.457370 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9a8), length 140
 10:35:31.475606 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9a9), length 140
 10:35:31.622315 IP 10.10.10.1.isakmp  10.10.10.2.isakmp: isakmp: phase
 2/others ? inf[E]
 10:35:31.622544 IP 10.10.10.2.isakmp  10.10.10.1.isakmp: isakmp: phase
 2/others ? inf[E]
 10:35:31.622658 IP 10.10.10.2.isakmp  10.10.10.1.isakmp: isakmp: phase
 2/others ? inf[E]
 10:35:31.623933 IP 10.10.10.1.isakmp  10.10.10.2.isakmp: isakmp: phase
 2/others ? inf[E]
 10:35:32.492349 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9aa), length 140
 10:35:33.509346 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9ab), length 140
 10:35:34.527187 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9ac), length 140
 10:35:35.539600 IP 10.10.10.2  10.10.10.1:
 ESP(spi=0x03081e58,seq=0x9ad), length 140

 With r285535 all works fine.


Right commit is in subject - r285336.
___
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: IPSEC stop works after r285336

[Alexandr Krivulya]

24.07.2015 13:19, Andrey V. Elsukov пишет:
 On 23.07.2015 10:38, Alexandr Krivulya wrote:
 I have IPSEC tunnel inside l2tp tunnel via mpd. After r285536 I see only
 outgoing esp packets on ng interface:
 What FreeBSD version do you use?
 Please check https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192774
 and your security policies configuration.


I think it is not my situation.
I'm using latest CURRENT r285833 with rules:

root@thinkpad:/usr/src # setkey -DP
0.0.0.0/0[any] 10.10.10.2[any] any
in ipsec
esp/tunnel/10.10.10.1-10.10.10.2/require
spid=3 seq=1 pid=14609
refcnt=1
10.10.10.2[any] 0.0.0.0/0[any] any
out ipsec
esp/tunnel/10.10.10.2-10.10.10.1/require
spid=4 seq=0 pid=14609
refcnt=1

In that bug L2TP use IPSEC in transport mode, but in my scenario IPSEC
in tunnel mode inside L2TP. And it works fine prior to r285536.
___
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: IPSEC stop works after r285336

[Alexandr Krivulya]

24.07.2015 15:13, Andrey V. Elsukov пишет:
 On 24.07.2015 15:10, Alexandr Krivulya wrote:
 In that bug L2TP use IPSEC in transport mode, but in my scenario IPSEC
 in tunnel mode inside L2TP. And it works fine prior to r285536.
 But r285536 didn't touch head's source. This is commit into stable/10.
 So, it can't break something in 11.0-CURRENT.


I mean this commit:
https://svnweb.freebsd.org/base?view=revisionrevision=285336

Sorry for my mistake
___
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

IPSEC stop works after r285336

[Alexandr Krivulya]

I have IPSEC tunnel inside l2tp tunnel via mpd. After r285536 I see only
outgoing esp packets on ng interface:

root@thinkpad:/usr/src # tcpdump -i ng0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ng0, link-type NULL (BSD loopback), capture size 262144 bytes
10:35:27.331886 IP 10.10.10.2  10.10.10.1:
ESP(spi=0x03081e58,seq=0x9a5), length 140
10:35:28.371707 IP 10.10.10.2  10.10.10.1:
ESP(spi=0x03081e58,seq=0x9a6), length 140
10:35:29.443536 IP 10.10.10.2  10.10.10.1:
ESP(spi=0x03081e58,seq=0x9a7), length 140
10:35:30.457370 IP 10.10.10.2  10.10.10.1:
ESP(spi=0x03081e58,seq=0x9a8), length 140
10:35:31.475606 IP 10.10.10.2  10.10.10.1:
ESP(spi=0x03081e58,seq=0x9a9), length 140
10:35:31.622315 IP 10.10.10.1.isakmp  10.10.10.2.isakmp: isakmp: phase
2/others ? inf[E]
10:35:31.622544 IP 10.10.10.2.isakmp  10.10.10.1.isakmp: isakmp: phase
2/others ? inf[E]
10:35:31.622658 IP 10.10.10.2.isakmp  10.10.10.1.isakmp: isakmp: phase
2/others ? inf[E]
10:35:31.623933 IP 10.10.10.1.isakmp  10.10.10.2.isakmp: isakmp: phase
2/others ? inf[E]
10:35:32.492349 IP 10.10.10.2  10.10.10.1:
ESP(spi=0x03081e58,seq=0x9aa), length 140
10:35:33.509346 IP 10.10.10.2  10.10.10.1:
ESP(spi=0x03081e58,seq=0x9ab), length 140
10:35:34.527187 IP 10.10.10.2  10.10.10.1:
ESP(spi=0x03081e58,seq=0x9ac), length 140
10:35:35.539600 IP 10.10.10.2  10.10.10.1:
ESP(spi=0x03081e58,seq=0x9ad), length 140

With r285535 all works fine.
___
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

laptop freezes when starting X

[Alexandr Krivulya]

Hello, community
After updating to r278893 my thinkpad e530 (Ivy bridge) freezes when
starting X after few seconds. There is no any such issues with my
previos kernel r278308. Both Xorg.0.log and messages doesn't have any
new error records. Changing hw.x2apic_enable does not make any difference.
___
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: drm2 regression: backlight adjustment on ivybridge no longer works

[Alexandr Krivulya]

01.02.2015 12:12, Lars Engels пишет:
 On Sun, Feb 01, 2015 at 10:41:25AM +0100, Lars Engels wrote:
 On Sun, Feb 01, 2015 at 03:35:15AM -0600, Andrew Wilcox wrote:
 Lars Engels sent: 01 February 2015 03:18:
 With acpi_video I get some interesting sysctl:
 hw.acpi.video.lcd0.levels: 100 100 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87
 88 89 90 91 92 93 94 95 96 97 98 99 100

 I guess it should not be 100 100 0 ... 100?
 Actually, the standard internal ACPI brightness level struct (BRTN in the 
 DSDT) is laid out as:

 * Full power value (one byte, the value at which the brightness should be 
 set on AC by default)
 * Economy value (one byte, the value at which the brightness should be 
 set on battery by default)
 * Actual values (N bytes, up to Max but frequently not)

 So, no, that value indeed sounds correct.  On my laptop the value is:
 80 47 0 7 13 20 27 33 40 47 53 60 67 73 80 87 93 100
 Thank you for the explanation.
 FWIW, here is the full output from sysctl hw.acpi.video.lcd0:

 hw.acpi.video.lcd0.active: 1
 hw.acpi.video.lcd0.brightness: 11
 hw.acpi.video.lcd0.fullpower: 100
 hw.acpi.video.lcd0.economy: 100
 hw.acpi.video.lcd0.levels: 100 100 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87
 88 89 90 91 92 93 94 95 96 97 98 99 100
 hw.acpi.video.crt0.active: 1
 hw.acpi.video.ext0.active: 1
 hw.acpi.video.ext1.active: 1
 hw.acpi.video.ext2.active: 1
 hw.acpi.video.ext3.active: 1
 hw.acpi.video.ext4.active: 1
 hw.acpi.video.ext5.active: 1

 What revision of -CURRENT are you running?  What is the outcome of
 trying the patch posted Saturday morning (UTC) from Elizabeth Myers
 (message ID 54cc5311.9070...@interlinked.me)?

 I'm currently running r277858 and haven't tried the patch, yet. But will
 do now and report back.

 So now I have a new sysctl hw.dri.0.i915_backlight. But no matter what
 value I pass to it, the brightness doesn't change.

 It's a Ivy Brigde notebook where drm shows some errors in dmesg. Please
 see: http://pastie.org/9877917



Please try to boot with acpi_ibm and without acpi_video. This way all
works for me.
___
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: Questions on adding backlight support for the i915 driver

[Alexandr Krivulya]

31.01.2015 10:30, Miguel Clara пишет:
 On Sat, Jan 31, 2015 at 8:19 AM, Elizabeth Myers elizab...@interlinked.me
 wrote:

 On 01/31/15 02:15, Miguel Clara wrote:
 Working fine on a HP running current as I've noted in the other thread
 as for the keys.
 This one (and most HP Pavillion models) use the Fn+F(2/3) but the keys,
 and my Acer (and I think not all are like this) use Fn+-/-
 If your keys work (as in, they do things in FreeBSD), does sysctl and
 the keys work together just fine with no weird effects?

 The only weird problem I could possibly think of that could come up is
 that the keys do a simple add/subtract to the PCM values, and so the
 brightness ends up wrong. See if that happens.


 Well, in the HP the keys don't do nothing it seems not even xev reports
 anything when I use them, but they could be wrongly mapped maybe...

 On the acer I do see keycodes from xev, but Im using lumina and If I try to
 map them to anything it doesn't work... I'll see what happens after reboot
 though.


All works fine (sysctl and Fn-keys) on my Thinkpad E530 with IvyBridge!
___
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: drm2 regression: backlight adjustment on ivybridge no longer works

[Alexandr Krivulya]

29.01.2015 12:46, Ranjan1018 . пишет:
 2015-01-28 10:11 GMT+01:00 Adrian Chadd adr...@freebsd.org:

 ugh, so because i can't sleep, I read the Linux i915 history for
 backlight changes.

 Turns out if I disable bit 30 in ivb_pch_pwm_override() to register
 BLC_PWM_PCH_CTL1, the acpi video setting works. The keyboard settings
 still don't, but I'll worry about that later.

 Bit 30 in the linux drm code is:

 #define   BLM_PCH_OVERRIDE_ENABLE   (1  30)

 The linux dri code doesn't set that for ivybridge - only for broadwell.

 (also, the linux driver has POSTING_READ() which I'm guessing is to
 ensure things made it out to the device and have been flushed before
 doing another IO operation.)

 I have my (via sysctl) panel backlight control working again.



 -adrian

 Thank you guys,
 the backlight control works again on my laptop with this patch, suggested
 by Adrian :

 --- sys/dev/drm2/i915/intel_display.c.orig   (revision 277487)
 +++ sys/dev/drm2/i915/intel_display.c(working copy)
 @@ -6995,7 +6995,7 @@
   */
  I915_WRITE(BLC_PWM_CPU_CTL2, PWM_ENABLE);
  I915_WRITE(BLC_PWM_CPU_CTL, 0);
 -I915_WRITE(BLC_PWM_PCH_CTL1, PWM_ENABLE | (130));
 +I915_WRITE(BLC_PWM_PCH_CTL1, PWM_ENABLE);
  }

  void intel_modeset_init_hw(struct drm_device *dev)


This patch fixes problem for me too, but only when acpi_video module is
not loaded. With acpi_video loaded I still see this errors (but it's
probably another topic):

Jan 29 19:02:27 thinkpad kernel: ACPI Exception: AE_AML_PACKAGE_LIMIT,
Index (0x000FF) is beyond end of object (length 0x16)
(20140926/exoparg2-452)
Jan 29 19:02:27 thinkpad kernel: ACPI Error: Method parse/execution
failed [\_SB_.PCI0.LPCB.EC0_.BRNS] (Node 0xf80007541b00),
AE_AML_PACKAGE_LIMIT (20140926/psparse-552)
Jan 29 19:02:27 thinkpad kernel: ACPI Error: Method parse/execution
failed [\_SB_.PCI0.VID_.LCD0._BCM] (Node 0xf80007550280),
AE_AML_PACKAGE_LIMIT (20140926/psparse-552)
Jan 29 19:02:27 thinkpad kernel: can't evaluate
\_SB_.PCI0.VID_.LCD0._BCM - AE_AML_PACKAGE_LIMIT
___
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: Child suspend/resume

[Alexandr Krivulya]

I've done three suspend/resume cycle during last workday and all works
fine. Sorry for misled.

13.08.2014 18:35, Justin Hibbits пишет:
 That's odd, because another tester reported everything worked correctly
 for him.  Could you send me the output of a verbose boot dmesg (boot
 -v), devinfo -rv, and pciconf -lv?

 Thanks,
 Justin

 On Wed, 13 Aug 2014 09:17:24 +0300
 Alexandr Krivulya shur...@shurik.kiev.ua wrote:

 Now laptop resumes, screen turned on and I see in dmesg acpi: resumed
 at ..., but neither keyboard nor mouse don't work and host is not
 accessible from network.

 12.08.2014 17:06, Justin Hibbits пишет:
 Hi Alexandr,

 Thanks.  I got another confirmation that it didn't work, and may
 have found the cause.  I have another patch that you can find at
 https://phabric.freebsd.org/D590 which fixes a typo that I had made.
 Could you try that?

 (Added current@ so everyone else sees this as well).

 Thanks!

 - Justin

 On Tue, 12 Aug 2014 11:18:29 +0300
 Alexandr Krivulya shur...@shurik.kiev.ua wrote:

 Hi, Justin
 After applying your patch my thinkpad e530 (FreeBSD 11.0-CURRENT,
 amd64) doesn't resume any more - screen remains black.

 11.08.2014 08:30, Justin Hibbits (by way of Justin Hibbits
 chmeeed...@gmail.com) пишет:
 Hi all,

 The attached patch is completely untested, due to lack of existing
 suspendable hardware (no x86 machines).  It does compile cleanly
 against head, though. I don't think it should change any behavior,
 I tried to keep the essence of the code path the same.

 It was suggested that I break up my multipass suspend/resume code
 into incremental parts, so this is part one.  It adds a
 BUS_SUSPEND_CHILD/BUS_RESUME_CHILD, as well as helper functions,
 bus_generic_suspend_child()/bus_generic_resume_child(), and
 modifies the PCI driver to use this new facility.

 I'd like some feedback, and testing of this, to make sure I didn't
 break anything.

 Thanks,
 Justin


 ___
 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

___
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: Child suspend/resume

[Alexandr Krivulya]

Now laptop resumes, screen turned on and I see in dmesg acpi: resumed
at ..., but neither keyboard nor mouse don't work and host is not
accessible from network.

12.08.2014 17:06, Justin Hibbits пишет:
 Hi Alexandr,

 Thanks.  I got another confirmation that it didn't work, and may have
 found the cause.  I have another patch that you can find at
 https://phabric.freebsd.org/D590 which fixes a typo that I had made.
 Could you try that?

 (Added current@ so everyone else sees this as well).

 Thanks!

 - Justin

 On Tue, 12 Aug 2014 11:18:29 +0300
 Alexandr Krivulya shur...@shurik.kiev.ua wrote:

 Hi, Justin
 After applying your patch my thinkpad e530 (FreeBSD 11.0-CURRENT,
 amd64) doesn't resume any more - screen remains black.

 11.08.2014 08:30, Justin Hibbits (by way of Justin Hibbits
 chmeeed...@gmail.com) пишет:
 Hi all,

 The attached patch is completely untested, due to lack of existing
 suspendable hardware (no x86 machines).  It does compile cleanly
 against head, though. I don't think it should change any behavior,
 I tried to keep the essence of the code path the same.

 It was suggested that I break up my multipass suspend/resume code
 into incremental parts, so this is part one.  It adds a
 BUS_SUSPEND_CHILD/BUS_RESUME_CHILD, as well as helper functions,
 bus_generic_suspend_child()/bus_generic_resume_child(), and modifies
 the PCI driver to use this new facility.

 I'd like some feedback, and testing of this, to make sure I didn't
 break anything.

 Thanks,
 Justin


 ___
 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

___
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: USB 2.0 webcam in virtualbox on CURRENT not working!

[Alexandr Krivulya]

17.07.2014 08:30, Sergey V. Dyatko пишет:
 On Wed, 16 Jul 2014 23:40:48 +0200
 Hans Petter Selasky h...@selasky.org wrote: 

 On 07/16/14 13:40, Maciej Milewski wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 16.07.2014 13:28, O. Hartmann wrote:
 I desperately need to have a SKYPE based chat with an offshore
 department. Since Skype is not a native port, I try to use a virtual
 box running Windows 7. And here the nightmare begins.

 Skype works in the VBox, but audio only. I have two WebCAMs here, a
 brand new Logitech C270 and a older Medion MD86511. The latter one can
 be seen in the device list of Windows 7 within the VBox, but can not be
 activated.

 More frustrating, the Logitech C270, doesn't work, it is not even seen
 by the VBox. I tested the cam on another Windows 7 system of a
 colleague and it works. FreeBSD does also see this USB Cam, but why
 is the device hidden for the VBox?
 What do you mean by saying see?
 usbconfig on freebsd lists it as ugen device?
 Is it attached to vbox machine by some filter?
 Have you tried VBoxManage usbfilter add?
 I'm currently using some kind of software security jingle device this way:
 VBoxManage usbfilter add 1 --target VMachineName --name USBKey
 --vendorid 0x --productid 0x
 But I haven't used any webcam this way.

 In the configuration, I have the ability to enable/disable USB 2.0
 subsystem. Enabled, VBox rejects to start on all FBSD around (9.3-PRE,
 11-CURRENT). What is that? Is VBox not capable of using USB 2.0
 devices in conjunction with FreeBSD?

 How to solve this? Is there a Skype 6 client for FreeBSD?

 Thanks in advance, please CC me,
 Oliver
 Hi,

 Skype:

 Mount this union with /usr/ports:

 https://github.com/cpu82/skype4-ports

 And then you can install skype and even use the video chat.
 Note: This GH repository is outdated, please, you should install or update 
 your
 ports tree from the following repository:

 https://github.com/xmj/linux-ports/

 xmj follow the instructions on https://github.com/xmj/linux-ports/

Does it planned to be merged into main ports tree?

___
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: [patch] USB after second suspend/resume on ThinkPads.

[Alexandr Krivulya]

18.06.2014 12:29, Edward Tomasz Napierała пишет:
 On 0618T1108, Alexandr Krivulya wrote:
 16.06.2014 22:21, Edward Tomasz Napierała пишет:
 Hi.  Patch below should fix a problem where USB stops working after
 _second_ suspend/resume, which happens on various ThinkPad models.
 Please test, and report both success stories and failures.  If nothing
 comes up, I'll commit it in a week or so.

 (Btw, has anyone encountered the problem on hardware other than ThinkPads?)


 Index: sys/dev/acpi_support/acpi_ibm.c
 ===
 --- sys/dev/acpi_support/acpi_ibm.c (revision 267417)
 +++ sys/dev/acpi_support/acpi_ibm.c (working copy)
 @@ -169,6 +169,9 @@ struct acpi_ibm_softc {
 int light_get_supported;
 int light_set_supported;
  
 +   /* USB power workaround */
 +   ACPI_HANDLE power_handle;
 +
 /* led(4) interface */
 struct cdev *led_dev;
 int led_busy;
 @@ -365,6 +368,7 @@ acpi_ibm_attach(device_t dev)
  {
 struct acpi_ibm_softc   *sc;
 devclass_t  ec_devclass;
 +   ACPI_STATUS status;
  
 ACPI_FUNCTION_TRACE((char *)(uintptr_t) __func__);
  
 @@ -448,6 +452,17 @@ acpi_ibm_attach(device_t dev)
 if (sc-light_set_supported)
 sc-led_dev = led_create_state(ibm_led, sc, thinklight, 
 sc-light_val);
  
 +   /*
 +* Obtain a handle to the power resource available on many models.
 +* This must be turned on manually upon resume. Otherwise the system
 +* may, for instance, resume from S3 with usb(4) powered down.
 +*/
 +   status = AcpiGetHandle(sc-handle, \\_SB.PCI0.LPC.EC.PUBS, 
 sc-power_handle);
 +   if (ACPI_FAILURE(status)) {
 +   device_printf(dev, Failed to get power handle\n);
 +   return (status);
 +   }
 +
 return (0);
  }
  
 @@ -476,6 +491,7 @@ static int
  acpi_ibm_resume(device_t dev)
  {
 struct acpi_ibm_softc *sc = device_get_softc(dev);
 +   ACPI_STATUS status;
  
 ACPI_FUNCTION_TRACE((char *)(uintptr_t) __func__);
  
 @@ -495,6 +511,15 @@ acpi_ibm_resume(device_t dev)
  
 acpi_ibm_sysctl_set(sc, i, val);
 }
 +   if (sc-power_handle != NULL) {
 +   status = AcpiEvaluateObject(sc-power_handle,
 +   _ON, NULL, NULL);
 +   if (ACPI_FAILURE(status)) {
 +   device_printf(dev, failed to switch %s on - %s\n,
 +   acpi_name(sc-power_handle),
 +   AcpiFormatException(status));
 +   }
 +   }
 ACPI_SERIAL_END(ibm);
  
 return (0);
 Hi. I've never seen this problem before on my ThinkPad E530. However, I
 have applied this patch and after reboot all sysctl oids related to
 acpi_ibm disappeared.

 root@thinkpad:/home/shurik # kldstat|grep ibm
 9 1 0x8219 77e8 acpi_ibm.ko

 root@thinkpad:/home/shurik # sysctl dev.acpi_ibm
 root@thinkpad:/home/shurik #

 And in dmesg I see this errors:

 root@thinkpad:/home/shurik # dmesg -a|grep ibm
 acpi_ibm0: IBM ThinkPad ACPI Extras on acpi0
 acpi_ibm0: Failed to get power handle
 device_attach: acpi_ibm0 attach returned 5
 Ok, I'll make that attach problem non-fatal.

 Just to make sure: without the patch you don't have any problems
 with USB after multiple suspend/resume cycles, and you don't use
 any workarounds to make it work, eg. setting the dev.uhci.0.wake=1,
 or making USB ports always powered on in BIOS?

Exactly. I have no any problems with USB. Average uptime is two-three
weeks with everyday suspend/resume cycle. And I don't use any special
settings related to usb in loader.conf or sysctl.conf. The only
difference with GENERIC - all usb support built and loaded as modules.
In my BIOS i have turned on such settings:

- USB Support
- UEFI BIOS Support
- Always On USB


___
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: [patch] USB after second suspend/resume on ThinkPads.

[Alexandr Krivulya]

19.06.2014 13:44, Edward Tomasz Napierała пишет:
 On 0619T0935, Alexandr Krivulya wrote:
 18.06.2014 12:29, Edward Tomasz Napierała пишет:
 On 0618T1108, Alexandr Krivulya wrote:
 16.06.2014 22:21, Edward Tomasz Napierała пишет:
 Hi.  Patch below should fix a problem where USB stops working after
 _second_ suspend/resume, which happens on various ThinkPad models.
 Please test, and report both success stories and failures.  If nothing
 comes up, I'll commit it in a week or so.

 (Btw, has anyone encountered the problem on hardware other than 
 ThinkPads?)


 Index: sys/dev/acpi_support/acpi_ibm.c
 ===
 --- sys/dev/acpi_support/acpi_ibm.c   (revision 267417)
 +++ sys/dev/acpi_support/acpi_ibm.c   (working copy)
 @@ -169,6 +169,9 @@ struct acpi_ibm_softc {
   int light_get_supported;
   int light_set_supported;
  
 + /* USB power workaround */
 + ACPI_HANDLE power_handle;
 +
   /* led(4) interface */
   struct cdev *led_dev;
   int led_busy;
 @@ -365,6 +368,7 @@ acpi_ibm_attach(device_t dev)
  {
   struct acpi_ibm_softc   *sc;
   devclass_t  ec_devclass;
 + ACPI_STATUS status;
  
   ACPI_FUNCTION_TRACE((char *)(uintptr_t) __func__);
  
 @@ -448,6 +452,17 @@ acpi_ibm_attach(device_t dev)
   if (sc-light_set_supported)
   sc-led_dev = led_create_state(ibm_led, sc, thinklight, 
 sc-light_val);
  
 + /*
 +  * Obtain a handle to the power resource available on many models.
 +  * This must be turned on manually upon resume. Otherwise the system
 +  * may, for instance, resume from S3 with usb(4) powered down.
 +  */
 + status = AcpiGetHandle(sc-handle, \\_SB.PCI0.LPC.EC.PUBS, 
 sc-power_handle);
 + if (ACPI_FAILURE(status)) {
 + device_printf(dev, Failed to get power handle\n);
 + return (status);
 + }
 +
   return (0);
  }
  
 @@ -476,6 +491,7 @@ static int
  acpi_ibm_resume(device_t dev)
  {
   struct acpi_ibm_softc *sc = device_get_softc(dev);
 + ACPI_STATUS status;
  
   ACPI_FUNCTION_TRACE((char *)(uintptr_t) __func__);
  
 @@ -495,6 +511,15 @@ acpi_ibm_resume(device_t dev)
  
   acpi_ibm_sysctl_set(sc, i, val);
   }
 + if (sc-power_handle != NULL) {
 + status = AcpiEvaluateObject(sc-power_handle,
 + _ON, NULL, NULL);
 + if (ACPI_FAILURE(status)) {
 + device_printf(dev, failed to switch %s on - %s\n,
 + acpi_name(sc-power_handle),
 + AcpiFormatException(status));
 + }
 + }
   ACPI_SERIAL_END(ibm);
  
   return (0);
 Hi. I've never seen this problem before on my ThinkPad E530. However, I
 have applied this patch and after reboot all sysctl oids related to
 acpi_ibm disappeared.

 root@thinkpad:/home/shurik # kldstat|grep ibm
 9 1 0x8219 77e8 acpi_ibm.ko

 root@thinkpad:/home/shurik # sysctl dev.acpi_ibm
 root@thinkpad:/home/shurik #

 And in dmesg I see this errors:

 root@thinkpad:/home/shurik # dmesg -a|grep ibm
 acpi_ibm0: IBM ThinkPad ACPI Extras on acpi0
 acpi_ibm0: Failed to get power handle
 device_attach: acpi_ibm0 attach returned 5
 Ok, I'll make that attach problem non-fatal.

 Just to make sure: without the patch you don't have any problems
 with USB after multiple suspend/resume cycles, and you don't use
 any workarounds to make it work, eg. setting the dev.uhci.0.wake=1,
 or making USB ports always powered on in BIOS?

 Exactly. I have no any problems with USB. Average uptime is two-three
 weeks with everyday suspend/resume cycle. And I don't use any special
 settings related to usb in loader.conf or sysctl.conf. The only
 difference with GENERIC - all usb support built and loaded as modules.
 In my BIOS i have turned on such settings:

 - USB Support
 - UEFI BIOS Support
 - Always On USB
 The last one is off by default, right?  Turning it on actually
 works around the problem in earlier Thinkpad models.  Could you
 try to set it to default (disable) and see if the problem still
 doesn't occur?

This option is enabled by default on my laptop. It allows to charge
mobile devices when laptop in sleep state or powered off via USB 2.0 port.
Now, I reset BIOS to default settings and turned off Always on USB,
boot to my old kernel without patch and do suspend/resume three times.
Both 3.0 and 2.0 USB ports works fine after each resume.
___
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: [patch] USB after second suspend/resume on ThinkPads.

[Alexandr Krivulya]

16.06.2014 22:21, Edward Tomasz Napierała пишет:
 Hi.  Patch below should fix a problem where USB stops working after
 _second_ suspend/resume, which happens on various ThinkPad models.
 Please test, and report both success stories and failures.  If nothing
 comes up, I'll commit it in a week or so.

 (Btw, has anyone encountered the problem on hardware other than ThinkPads?)


 Index: sys/dev/acpi_support/acpi_ibm.c
 ===
 --- sys/dev/acpi_support/acpi_ibm.c   (revision 267417)
 +++ sys/dev/acpi_support/acpi_ibm.c   (working copy)
 @@ -169,6 +169,9 @@ struct acpi_ibm_softc {
   int light_get_supported;
   int light_set_supported;
  
 + /* USB power workaround */
 + ACPI_HANDLE power_handle;
 +
   /* led(4) interface */
   struct cdev *led_dev;
   int led_busy;
 @@ -365,6 +368,7 @@ acpi_ibm_attach(device_t dev)
  {
   struct acpi_ibm_softc   *sc;
   devclass_t  ec_devclass;
 + ACPI_STATUS status;
  
   ACPI_FUNCTION_TRACE((char *)(uintptr_t) __func__);
  
 @@ -448,6 +452,17 @@ acpi_ibm_attach(device_t dev)
   if (sc-light_set_supported)
   sc-led_dev = led_create_state(ibm_led, sc, thinklight, 
 sc-light_val);
  
 + /*
 +  * Obtain a handle to the power resource available on many models.
 +  * This must be turned on manually upon resume. Otherwise the system
 +  * may, for instance, resume from S3 with usb(4) powered down.
 +  */
 + status = AcpiGetHandle(sc-handle, \\_SB.PCI0.LPC.EC.PUBS, 
 sc-power_handle);
 + if (ACPI_FAILURE(status)) {
 + device_printf(dev, Failed to get power handle\n);
 + return (status);
 + }
 +
   return (0);
  }
  
 @@ -476,6 +491,7 @@ static int
  acpi_ibm_resume(device_t dev)
  {
   struct acpi_ibm_softc *sc = device_get_softc(dev);
 + ACPI_STATUS status;
  
   ACPI_FUNCTION_TRACE((char *)(uintptr_t) __func__);
  
 @@ -495,6 +511,15 @@ acpi_ibm_resume(device_t dev)
  
   acpi_ibm_sysctl_set(sc, i, val);
   }
 + if (sc-power_handle != NULL) {
 + status = AcpiEvaluateObject(sc-power_handle,
 + _ON, NULL, NULL);
 + if (ACPI_FAILURE(status)) {
 + device_printf(dev, failed to switch %s on - %s\n,
 + acpi_name(sc-power_handle),
 + AcpiFormatException(status));
 + }
 + }
   ACPI_SERIAL_END(ibm);
  
   return (0);
Hi. I've never seen this problem before on my ThinkPad E530. However, I
have applied this patch and after reboot all sysctl oids related to
acpi_ibm disappeared.

root@thinkpad:/home/shurik # kldstat|grep ibm
9 1 0x8219 77e8 acpi_ibm.ko

root@thinkpad:/home/shurik # sysctl dev.acpi_ibm
root@thinkpad:/home/shurik #

And in dmesg I see this errors:

root@thinkpad:/home/shurik # dmesg -a|grep ibm
acpi_ibm0: IBM ThinkPad ACPI Extras on acpi0
acpi_ibm0: Failed to get power handle
device_attach: acpi_ibm0 attach returned 5
sysctl: unknown oid 'dev.acpi_ibm.0.events' at line 22: No such file or
directory
sysctl: unknown oid 'dev.acpi_ibm.0.fan' at line 23: No such file or
directory
sysctl: unknown oid 'dev.acpi_ibm.0.bluetooth' at line 24: No such file
or directory
acpi_ibm0: IBM ThinkPad ACPI Extras on acpi0
#5 0x8260766c at acpi_ibm_attach+0x5bc
acpi_ibm0: IBM ThinkPad ACPI Extras on acpi0
acpi_ibm0: Failed to get power handle
device_attach: acpi_ibm0 attach returned 5



All Fn keys and usb ports still work fine before/after suspend/resume.
___
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: iwn(4) in -HEAD supporting Centrino Wireless-N 135

[Alexandr]

May be it is similar to my problem. It connects to AP for a few seconds
and then drop a connection. It situation 100% reproducible in 11n mode,
but in 11g works fine.

http://docs.freebsd.org/cgi/mid.cgi?5304B48E.8070404

26.02.2014 17:09, Adrian Chadd пишет:
 Hi,

 Yeah, there's likely something missing. But I just at the moment have
 no time to debug this.


 -a


 On 26 February 2014 04:37, Tom Murphy free...@pertho.net wrote:
 Hi all,

   I compiled a fresh kernel from -HEAD and rebooted in the hope that my
 laptop's wifi would now be supported (I saw the commit messages in January
 about it possibly supporting Centrino Wireless-N 135). However, while
 it does attempt to bring the wifi up, the link just goes up and down
 and does not work properly.

   Knowing that the BSDs are fairly close and share some code, I did try
 the OpenBSD driver and it works. Is there some code that could be missing
 from the FreeBSD iwn(4) to stabilize it? I'd be happy to test any patches.

 Kind regards,
 Tom

 wlan0: no link ..wlan0: link state changed to UP
 wlan0 link stage up - down
 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
 wlan0: link state changed to UP
 wlan0: link state down - up
 (more DHCPDISCOVER)
 wlan0 link stage up - down

 Rise and repeat.

 iwn0: Intel Centrino Wireless-N 135 mem 0xf790-0xf7901fff irq 18 at 
 device 0.0 on pci3

 ___
 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

___
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: iwn(4) in -HEAD supporting Centrino Wireless-N 135

[Alexandr]

Tom, could you:

1. compile kernel WITH_IWNDEBUG
2. sysctl dev.iwn.0.debug=0x1
3. wlandebug -i wlan0 auth+assoc
4. Associate with AP in 11n mode
5. Send us appropriate /var/log/messages

Then I try to compare it with my log.

27.02.2014 09:32, Adrian Chadd пишет:
 Yeah, try to verify if it's this or not.

 It's quite possible that there's some NIC setup for 11n that isn't
 completely correct.


 -a



 On 26 February 2014 23:23, Alexandr shur...@shurik.kiev.ua wrote:
 May be it is similar to my problem. It connects to AP for a few seconds
 and then drop a connection. It situation 100% reproducible in 11n mode,
 but in 11g works fine.

 http://docs.freebsd.org/cgi/mid.cgi?5304B48E.8070404

 26.02.2014 17:09, Adrian Chadd пишет:
 Hi,

 Yeah, there's likely something missing. But I just at the moment have
 no time to debug this.


 -a


 On 26 February 2014 04:37, Tom Murphy free...@pertho.net wrote:
 Hi all,

   I compiled a fresh kernel from -HEAD and rebooted in the hope that my
 laptop's wifi would now be supported (I saw the commit messages in January
 about it possibly supporting Centrino Wireless-N 135). However, while
 it does attempt to bring the wifi up, the link just goes up and down
 and does not work properly.

   Knowing that the BSDs are fairly close and share some code, I did try
 the OpenBSD driver and it works. Is there some code that could be missing
 from the FreeBSD iwn(4) to stabilize it? I'd be happy to test any patches.

 Kind regards,
 Tom

 wlan0: no link ..wlan0: link state changed to UP
 wlan0 link stage up - down
 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
 wlan0: link state changed to UP
 wlan0: link state down - up
 (more DHCPDISCOVER)
 wlan0 link stage up - down

 Rise and repeat.

 iwn0: Intel Centrino Wireless-N 135 mem 0xf790-0xf7901fff irq 18 at 
 device 0.0 on pci3

 ___
 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
 ___
 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: [CURRENT]: claws-mail and firefox fail with Invalid alignment

[Alexandr]

21.02.2014 20:03, O. Hartmann пишет:
 On Fri, 21 Feb 2014 19:00:13 +0100
 O. Hartmann ohart...@zedat.fu-berlin.de wrote:

 On Fri, 21 Feb 2014 18:49:13 +0100
 Dimitry Andric d...@freebsd.org wrote:

 On 21 Feb 2014, at 18:40, O. Hartmann ohart...@zedat.fu-berlin.de
 wrote:
 On every FreeBSD 11.0-CURRENT #0 r262294: Fri Feb 21 14:11:20 CET
 2014 amd64 I run neither claws-mail nor firfox run after the last
 buildworld. They fail both with the error

 Invalid alignment

 Does anyone see this problem too? I tried to recompile claws-mail
 and firefox, but without success (compilation succeeded, but the
 error stays).

 What happened here? How to solve? 
 Can you try reverting r262277, rebuilding libexec/rtld-elf and
 reinstalling it, and seeing if that fixes it?

 -Dimitry

 Hello Dimitry,

 in r262277 there is no change in libexec/rtld-elf, I had to go back to
 r262270. I did as requested and reinstalling libexec/rtld-elf fixes
 the reported issue.

 Regards,
 Oliver
 Sorry, it is r262276


I have the same issue with firefox and thunderbird. Reverting
libexec/rtld-elf to r262276 solves a problem.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: where is the startkde file of kde4

[Alexandr]

21.07.2013 16:13, Robin Lehrmann пишет:
 hello mailing-list, 
 I have installed kde4 on the current freebsd. 

 Now I want to start it but I don't find the start script in 
 /usr/local/kde4/bin

 I try the scripts kde4 kded4 kdeinit4 but I get always the error $Display is 
 Not Set 

 how can I set the display or start kde4?

 - Robin Lehrmann

Do you have kdm4_enable=YES in your rc.conf? If you not, please add it
and use

service kdm4 start
___
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: Memstick Images not working (mountroot prompt)

[Alexandr]

I have the same problem, that I resolve by changing boot order in the
bios settings to usb-drive as first boot device. (note, not in quick
boot order menu).


05.06.2013 22:11, Miguel Clara пишет:
 Done:

 http://www.freebsd.org/cgi/query-pr.cgi?pr=179342



 On Wed, Jun 5, 2013 at 7:45 PM, Glen Barber g...@freebsd.org wrote:
 Ok.  Please open a PR as Adrian suggested, so we can properly track
 this.

 Glen

 On Wed, Jun 05, 2013 at 06:42:05PM +, miguelmcl...@gmail.com wrote:
 Sadly it doesn't... Just two ports in the back and in the same controller.

 Its an Intel Panter Point controller, but I'll add that info to the PR as 
 soon has my girlfriend get out of farmville and let's me use her laptop xD

 Note: I also tried sysctl hw.xhci.xhci_port_route=-1 and =1 has I wasn't 
 sure what would be correct but none of those helped!

 Thanks
 Enviado a partir do meu smartphone BlackBerry® www.blackberry.com

 -Original Message-
 From: Glen Barber g...@freebsd.org
 Date: Wed, 5 Jun 2013 14:08:00
 To: Miguel Claramiguelmcl...@gmail.com
 Cc: freebsd-current@freebsd.org
 Subject: Re: Memstick Images not working (mountroot prompt)

 On Wed, Jun 05, 2013 at 03:52:44PM +0100, Miguel Clara wrote:
 Forgot to CC the list, sorry!

 In the meantime I upgrade from 9.1 using the base and kernel tarballs,
 I could boot and I have wireless supported!

 I have my ssd encrypted and the hdd too, the hdd is encrypted with
 passphrase + key, and this key is in a usb stick (a different one form
 the other two already tried).

 The USB stick is not working to, and I also tried a USB Western
 Digital 500GB disk, no luck either!

 So no usb support basically...

 dmesg output after connecting the device:

 xhci_do_comand: Command timeout!
 usb_alloc_device: device init 2 failed (USB_ERR_TIMEOUT, ignored)
 usbgen0.2: Unknown at usbus0 (disconnected)
 usb_reattach_port: could not allocate new device


 Also note that usbus0 is a 3.0 as dmesg shows after boot:
 usbus0: waiting for BIOS to give up control
 usbus0 on xhci0
 usbus0: 5.0Gpbs Super Speed USB v 3.0
 

 So I guess this is indeed a problem in the 10.0-current kernel, not
 sure what it could be or what more can I do to debug though...

 Please advice,

 Hmm.  Can you please try with a USB 2.0 port on the laptop?  (Hopefully
 it has at least one non-USB-3.0 port...)

 Glen


 ___
 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

Intel Wireless-N 2230 support

[Alexandr]

Hello!
Can anyone tell me about work on supporting this card by iwn(4)?

___
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: stable/9 r225827 i386 panic: vm_page_unwire: page 0xc2a38dc8's wire count is zero

[Alexandr Kovalenko]

On Thu, Sep 29, 2011 at 3:30 PM, Kostik Belousov kostik...@gmail.com wrote:
 On Thu, Sep 29, 2011 at 02:52:31PM +0300, Alexandr Kovalenko wrote:
 Hello!

 I'm running 9.0-BETA3 (r225827) and now rebuilding all my 1215 ports
 (I've upgraded from 8.2). I'm getting panic. Is it known
 problem/already fixed somewhere?

 FreeBSD mile.xxx.ua 9.0-BETA3 FreeBSD 9.0-BETA3 #0 r225827: Wed Sep 28
 17:11:17 EEST 2011     r...@mile.xxx.ua:/usr/obj/usr/src/sys/mile-9
 i386

 Unread portion of the kernel message buffer:
 panic: vm_page_unwire: page 0xc2a38dc8's wire count is zero
 cpuid = 1
 Uptime: 16h6m53s
 Physical memory: 1904 MB
 Dumping 367 MB: 352 336 320 304 288 272 256 240 224 208 192 176 160
 144 128 112 96 80 64 48 32 16

 #0  doadump (textdump=1) at pcpu.h:244
 #1  0xc071e5cb in kern_reboot (howto=260)
     at /usr/src/sys/kern/kern_shutdown.c:442
 #2  0xc071e82b in panic (fmt=Variable fmt is not available.
 ) at /usr/src/sys/kern/kern_shutdown.c:607
 #3  0xc0966903 in vm_page_unwire (m=0xc2a38dc8, activate=0)
     at /usr/src/sys/vm/vm_page.c:1905
 Please do frame 2, then p/x *m and show the result.

(kgdb) frame 2
#2  0xc071e82b in panic (fmt=Variable fmt is not available.) at
/usr/src/sys/kern/kern_shutdown.c:607
607 kern_reboot(bootopt);
(kgdb) p/x *m
No symbol m in current context.


 #4  0xc0796b80 in vfs_vmio_release (bp=0xde8bcbf4)
     at /usr/src/sys/kern/vfs_bio.c:1638
 #5  0xc0798813 in getnewbuf (vp=0xc6ea3550, slpflag=0, slptimeo=0,
     size=16384, maxsize=16384, gbflags=0) at /usr/src/sys/kern/vfs_bio.c:1949
 #6  0xc0799f2a in getblk (vp=0xc6ea3550, blkno=2520, size=16384, slpflag=0,
     slptimeo=0, flags=Variable flags is not available.
 ) at /usr/src/sys/kern/vfs_bio.c:2788
 #7  0xc079d49c in cluster_rbuild (vp=0xc6ea3550, filesize=44505088, lbn=2520,
     blkno=1209440, size=16384, run=Variable run is not available.
 ) at /usr/src/sys/kern/vfs_cluster.c:332
 #8  0xc079e145 in cluster_read (vp=0xc6ea3550, filesize=44505088,
     lblkno=2520, size=16384, cred=0x0, totread=1024, seqcount=7,
     bpp=0xf5824b60) at /usr/src/sys/kern/vfs_cluster.c:254
 #9  0xc0934cf5 in ffs_read (ap=0xf5824bac)
     at /usr/src/sys/ufs/ffs/ffs_vnops.c:514
 #10 0xc09ccb92 in VOP_READ_APV (vop=0xc0aa6a80, a=0xf5824bac)
     at vnode_if.c:887
 #11 0xc07c1120 in vn_read (fp=0xc5474508, uio=0xf5824c48,
     active_cred=0xc56a4d80, flags=1, td=0xc5b76b80) at vnode_if.h:384
 #12 0xc076380e in dofileread (td=0xc5b76b80, fd=3, fp=0xc5474508,
     auio=0xf5824c48, offset=41189376, flags=1) at file.h:254
 #13 0xc07639f5 in kern_preadv (td=0xc5b76b80, fd=3, auio=0xf5824c48,
     offset=41189376) at /usr/src/sys/kern/sys_generic.c:288
 #14 0xc0763b0d in sys_pread (td=0xc5b76b80, uap=0xf5824cec)
     at /usr/src/sys/kern/sys_generic.c:189
 #15 0xc09accf5 in syscall (frame=0xf5824d28) at subr_syscall.c:131
 #16 0xc0996db1 in Xint0x80_syscall ()
     at /usr/src/sys/i386/i386/exception.s:266
 #17 0x0033 in ?? ()
 Previous frame inner to this frame (corrupt stack?)

 --
 Alexandr Kovalenko
 http://uafug.org.ua/
 ___
 freebsd-sta...@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org




-- 
Alexandr Kovalenko
http://uafug.org.ua/
___
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: stable/9 r225827 i386 panic: vm_page_unwire: page 0xc2a38dc8's wire count is zero

[Alexandr Kovalenko]

2011/9/29 Kostik Belousov kostik...@gmail.com:
 On Thu, Sep 29, 2011 at 03:47:19PM +0300, Alexandr Kovalenko wrote:
 On Thu, Sep 29, 2011 at 3:30 PM, Kostik Belousov kostik...@gmail.com wrote:
  On Thu, Sep 29, 2011 at 02:52:31PM +0300, Alexandr Kovalenko wrote:
  Hello!
 
  I'm running 9.0-BETA3 (r225827) and now rebuilding all my 1215 ports
  (I've upgraded from 8.2). I'm getting panic. Is it known
  problem/already fixed somewhere?
 
  FreeBSD mile.xxx.ua 9.0-BETA3 FreeBSD 9.0-BETA3 #0 r225827: Wed Sep 28
  17:11:17 EEST 2011     r...@mile.xxx.ua:/usr/obj/usr/src/sys/mile-9
  i386
 
  Unread portion of the kernel message buffer:
  panic: vm_page_unwire: page 0xc2a38dc8's wire count is zero
  cpuid = 1
  Uptime: 16h6m53s
  Physical memory: 1904 MB
  Dumping 367 MB: 352 336 320 304 288 272 256 240 224 208 192 176 160
  144 128 112 96 80 64 48 32 16
 
  #0  doadump (textdump=1) at pcpu.h:244
  #1  0xc071e5cb in kern_reboot (howto=260)
      at /usr/src/sys/kern/kern_shutdown.c:442
  #2  0xc071e82b in panic (fmt=Variable fmt is not available.
  ) at /usr/src/sys/kern/kern_shutdown.c:607
  #3  0xc0966903 in vm_page_unwire (m=0xc2a38dc8, activate=0)
      at /usr/src/sys/vm/vm_page.c:1905
  Please do frame 2, then p/x *m and show the result.

 (kgdb) frame 2
 frame 3, sorry. p/x *(struct vm_page *)0xc2a38dc8 will do it as well.

(kgdb) frame 3
#3  0xc0966903 in vm_page_unwire (m=0xc2a38dc8, activate=0) at
/usr/src/sys/vm/vm_page.c:1905
1905panic(vm_page_unwire: page %p's wire count is
zero, m);
(kgdb) p/x *(struct vm_page *)0xc2a38dc8
$1 = {pageq = {tqe_next = 0xc2a38e10, tqe_prev = 0xc282a2b0}, listq =
{tqe_next = 0xc2a38e10, tqe_prev = 0xc282a2b8}, left = 0x0, right =
0x0, object = 0xc5725770, pindex = 0xbd3, phys_addr = 0x56a32000, md =
{pv_list = {tqh_first = 0xc3cc6418, tqh_last = 0xc3cc641c},
pat_mode = 0x6}, queue = 0x1, segind = 0x2, hold_count = 0x0,
order = 0xb, pool = 0x0, cow = 0x0, wire_count = 0x0, aflags = 0x3,
flags = 0x0, oflags = 0x0, act_count = 0x5, busy = 0x0, valid = 0xff,
dirty = 0xff}


 #2  0xc071e82b in panic (fmt=Variable fmt is not available.) at
 /usr/src/sys/kern/kern_shutdown.c:607
 607             kern_reboot(bootopt);
 (kgdb) p/x *m
 No symbol m in current context.


  #4  0xc0796b80 in vfs_vmio_release (bp=0xde8bcbf4)
      at /usr/src/sys/kern/vfs_bio.c:1638
  #5  0xc0798813 in getnewbuf (vp=0xc6ea3550, slpflag=0, slptimeo=0,
      size=16384, maxsize=16384, gbflags=0) at 
  /usr/src/sys/kern/vfs_bio.c:1949
  #6  0xc0799f2a in getblk (vp=0xc6ea3550, blkno=2520, size=16384, 
  slpflag=0,
      slptimeo=0, flags=Variable flags is not available.
  ) at /usr/src/sys/kern/vfs_bio.c:2788
  #7  0xc079d49c in cluster_rbuild (vp=0xc6ea3550, filesize=44505088, 
  lbn=2520,
      blkno=1209440, size=16384, run=Variable run is not available.
  ) at /usr/src/sys/kern/vfs_cluster.c:332
  #8  0xc079e145 in cluster_read (vp=0xc6ea3550, filesize=44505088,
      lblkno=2520, size=16384, cred=0x0, totread=1024, seqcount=7,
      bpp=0xf5824b60) at /usr/src/sys/kern/vfs_cluster.c:254
  #9  0xc0934cf5 in ffs_read (ap=0xf5824bac)
      at /usr/src/sys/ufs/ffs/ffs_vnops.c:514
  #10 0xc09ccb92 in VOP_READ_APV (vop=0xc0aa6a80, a=0xf5824bac)
      at vnode_if.c:887
  #11 0xc07c1120 in vn_read (fp=0xc5474508, uio=0xf5824c48,
      active_cred=0xc56a4d80, flags=1, td=0xc5b76b80) at vnode_if.h:384
  #12 0xc076380e in dofileread (td=0xc5b76b80, fd=3, fp=0xc5474508,
      auio=0xf5824c48, offset=41189376, flags=1) at file.h:254
  #13 0xc07639f5 in kern_preadv (td=0xc5b76b80, fd=3, auio=0xf5824c48,
      offset=41189376) at /usr/src/sys/kern/sys_generic.c:288
  #14 0xc0763b0d in sys_pread (td=0xc5b76b80, uap=0xf5824cec)
      at /usr/src/sys/kern/sys_generic.c:189
  #15 0xc09accf5 in syscall (frame=0xf5824d28) at subr_syscall.c:131
  #16 0xc0996db1 in Xint0x80_syscall ()
      at /usr/src/sys/i386/i386/exception.s:266
  #17 0x0033 in ?? ()
  Previous frame inner to this frame (corrupt stack?)
 
  --
  Alexandr Kovalenko
  http://uafug.org.ua/
  ___
  freebsd-sta...@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-stable
  To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
 



 --
 Alexandr Kovalenko
 http://uafug.org.ua/




-- 
Alexandr Kovalenko
http://uafug.org.ua/
___
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: Call for Test and Review: bwn(4) - another Broadcom Wireless driver

[Alexandr Rybalko]

On Wed, 3 Mar 2010 00:28:33 -0800
Weongyo Jeong weongyo.je...@gmail.com wrote:

 On Mon, Mar 01, 2010 at 10:32:40AM +0200, Alexandr Rybalko wrote:
  On Sun, 28 Feb 2010 01:52:59 -0800
  Weongyo Jeong weongyo.je...@gmail.com wrote:
  
  Can You test your driver without siba_switchcore, I see the device
  have mapping for all cores on SSB?
 
 I see what you mean.  siba_core.c which depends on PCI code would be
 compiled when it builds on SENTRY5.  So it looks currently it needs a
 patch to compile siba bus code without PCI code.  I'll try to make a
 patch.

I now trying to make bus independent interface, not done yet.
When finish, I send to You for review and maybe test.

 
   ssb0: Broadcom BCM4315 802.11b/g Wireless mem 0xf400-0xf4003fff 
  Think thre is 4 cores.
  When SSB on nexus, we don`t need core switching, maybe on PCI too.
 
 I think this is a difference between siba(4) and siba_bwn currently and
 it's one of TODOs we should solve to merge two codes.
 
 AFAIK approach to access each cores isn't same; it looks siba(4) creates
 devices for each cores so it'd not need to switch cores.  But siba_bwn
 doesn't do it like siba(4) so it needs to switch cores because all are
 handled on one device.

Look into this line:
ssb0: Broadcom BCM4315 802.11b/g Wireless mem 0xf400-0xf4003fff 
There we see, device have 0x4000 memory window. Each core required 0x1000.
Your code to call required core move PCI window to appropriate 0x1000 block 
(if core - second, move to 0xf4001000).
Maybe we can map full window, and then access to required core without core 
switching.

 
 regards,
 Weongyo Jeong
 


-- 
Рыбалко Александр
Консультант D-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: Call for Test and Review: bwn(4) - another Broadcom Wireless driver

[Alexandr Rybalko]

On Sun, 28 Feb 2010 01:52:59 -0800
Weongyo Jeong weongyo.je...@gmail.com wrote:

 On Sat, Feb 27, 2010 at 01:15:35AM +0200, Alex RAY wrote:
  Hi Weongyo,
  
  Can new siba release operate in systems like in this SVG image?
  System example: CPU BCM5836 + Wi-Fi BCM4318
 
 Recent changes of siba(4) by myself doesn't change code flow, layout and
 doesn't include enhancements if you're an user of SENTRY5 mips CPU (like
 BCM5836)
 
 All I did on recent changes were to put common routines or codes which
 could be used for original siba(4).  These codes are only used for
 bwn(4) driver currently and don't be merged with original siba(4).  That
 means there are two separated codes in current siba(4) so merging two
 into one is a TODO.
 
 I have no idea current siba(4) supports a system using on CPU BCM5836 +
 Wi-Fi BCM4318 but in theory it should work without problems though I
 didn't test.
 
  And can we compile siba bus code without pci code?
 
 I think it looks that it could be possible to compile without pci code.
 But makes sure that your device doesn't have PCI core.
 
 regards,
 Weongyo Jeong
 

Can You test your driver without siba_switchcore, I see the device have mapping 
for all cores on SSB?
 ssb0: Broadcom BCM4315 802.11b/g Wireless mem 0xf400-0xf4003fff 
Think thre is 4 cores.

When SSB on nexus, we don`t need core switching, maybe on PCI too.


-- 
Alexandr Rybalko r...@dlink.ua 
aka Alex RAY r...@ddteam.net
___
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

mdmfs: newfs exited with error code 36

[Deiter Alexandr Valerievich]

mdmfs don't work on CURRENT diskless sparc64:

Loading configuration files.
Entropy harvesting: interrupts ethernet point_to_point.
Starting file system checks:
nfs: can't update /var/db/mounttab for 1.1.1.1:/sparc64/netboot
cp: utmp: Read-only file system
/etc/rc.d/cleanvar: cannot create /var/run/clean_var: Read-only file system
+++ mount_md of /var
mdmfs: newfs exited with error code 36
nfs: can't update /var/db/mounttab for 1.1.1.1:/sparc64/netboot
.
dropping into shell, ^D to continue anyway.

# mdmfs -i 4096 -s 32m -M md /var
mdmfs: newfs exited with error code 36
# mdmfs -i 4096 -s 16m -M md /var
# df -h
Filesystem Size   Used  Avail Capacity  Mounted
on
1.1.1.1:/sparc64/netboot16G   3.0G11G21%/
devfs  1.0K   1.0K 0B   100%/dev
/dev/md215M   2.0K14M 0%/var
# top
last pid:   124;  load averages:  0.01,  0.05,  0.03  up 0+00:09:58
23:30:01
4 processes:   1 running, 3 sleeping
Mem: 2864K Active, 1544K Inact, 10M Wired, 40K Cache, 3392K Buf, 472M Free
Swap:
  PID USERNAME PRI NICE   SIZERES STATETIME   WCPUCPU COMMAND
   93 root   80  5440K  1448K wait 0:00  0.00%  0.00% sh
   35 root   80  5408K  1408K wait 0:00  0.00%  0.00% sh
  109 root   80  5216K  1320K wait 0:00  0.00%  0.00% sh
  124 root  960  6808K  1480K RUN  0:00  0.00%  0.00% top

P.S. On current 20030825 diskless operations works fine.

Thanks!


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Mozilla 1.0 error

[Alexandr Kovalenko]

Hello, Kris Kennaway!

On Fri, Jun 07, 2002 at 02:02:52PM -0700, you wrote:

 On Fri, Jun 07, 2002 at 04:56:45PM -0400, Joe Marcus Clarke wrote:
  On Fri, 2002-06-07 at 10:52, Jun Kuriyama wrote:
   At Fri, 7 Jun 2002 12:43:27 + (UTC),
   John Angelmo wrote:
  (cd /usr/ports/www/mozilla/work/mozilla/dist/bin;  /usr/bin/env
  LD_LIBRARY_PATH=. MOZILLA_FIVE_HOME=. ./regxpcom;  echo
  skin,install,select,classic/1.0  chrome/installed-chrome.txt;  echo
  locale,install,select,en-US  chrome/installed-chrome.txt;
  /usr/bin/env LD_LIBRARY_PATH=. MOZILLA_FIVE_HOME=. ./regchrome)
  [1]   Segmentation fault (core dumped)
  *** Error code 139

  Stop in /usr/ports/www/mozilla.
   I got same result, too.
  This problem seems to happen on -CURRENT and alpha -stable.
 And i386 -stable.
Worked fine for me:
[never@mile ~]$ cat /usr/ports/www/mozilla/Makefile | grep \$FreeBSD
# $FreeBSD: ports/www/mozilla/Makefile,v 1.107 2002/06/06 18:52:31 sobomax Exp $
[never@mile ~]$ uname -a
FreeBSD mile.nevermind.kiev.ua 4.6-RC FreeBSD 4.6-RC #0: Wed Jun  5 21:12:35 EEST 2002 
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/mile  i386
[never@mile ~]$ gcc -v
Using builtin specs.
gcc version 2.95.3 20010315 (release) [FreeBSD]

-- 
NEVE-RIPE
Ukrainian FreeBSD User Group
http://uafug.org.ua/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

error in buildworld

[Alexandr Listopad]

I had this error always, since I install 4.0-C
`make -k buildworld' helps, but it is no way for build world.


=== share/doc/usd/19.memacros
touch _stamp.extraobjs
(cd /usr/src/share/doc/usd/19.memacros; groff -mtty-char -Tascii -me -o1-
/usr/s
rc/share/doc/usd/19.memacros/intro.me) |  gzip -cn  paper.ascii.gz
=== share/doc/usd/20.meref
touch _stamp.extraobjs
(cd /usr/src/share/doc/usd/20.meref; groff -mtty-char -Tascii -me -o1-
/usr/src/
share/doc/usd/20.meref/ref.me) |  gzip -cn  paper.ascii.gz
/usr/src/share/doc/usd/20.meref/ref.me:1953: a space character is not
allowed in
 an escape name
=== share/doc/usd/30.rogue
make: don't know how to make rogue.me. Stop
*** Error code 2

Stop in /usr/src/share/doc/usd.
*** Error code 1

Stop in /usr/src/share/doc.
*** Error code 1



Thanks.

--
 Laa.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Problems make installworld

[Alexandr Listopad]

cd src/usr.bin/xinstall
make all install
cd ../../
make installworld

;)

I'm already have some experience in this problem... ;=|


bauerWhenever I try to do a 'make installworld' the following error occurs:
bauer
bauer/usr/libexec/ld-elf.so.1: install: Undefined symbol "setflags"
bauer
bauerWhen I do a 'make -k installworld', make continues but the error occurs
bauerseveral times.
bauerWhen I do a simple 'make installworld' the followin happens :
bauer
bauerinstall -c -s -o root -g wheel -m 444   -fschg  libscrypt.so.2 /usr/lib
bauer/usr/libexec/ld-elf.so.1: install: Undefined symbol "setflags"
bauer*** Error code 1
bauer
bauerStop in /usr/src/lib/libcrypt.
bauer*** Error code 1
bauer
bauerStop in /usr/src/lib.
bauer*** Error code 1
bauer
bauerStop in /usr/src.
bauer*** Error code 1
bauer
bauerI really hope someone can help me, cause I want to test the IPv6 things
bauerin 4.0 soon (for my thesis)
bauer
bauerThanx,
bauer
bauerKurt
bauer
bauer
bauer
bauer
bauerTo Unsubscribe: send mail to [EMAIL PROTECTED]
bauerwith "unsubscribe freebsd-current" in the body of the message
bauer

Regards,
  Listopad Alexandr
  ([EMAIL PROTECTED]), LAA7-RIPE
  ZGIA, Zaporozhye, Ukraine. 
  http://www.zgia.zp.ua. 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: error in installworld

[Alexandr Listopad]

sorry guys...

I already fix this... sorry.

And also I'm new in CURRENT.
Now I subscribe to 'freebsd-current' mailing list... and I hope I never
ask you so dummy questions.

Thanks you all for your answers!!!

sorry!

krisOn Thu, 3 Feb 2000, Charlie Root wrote:
kris
kris install -c -s -o root -g wheel -m 4555  -fschg rcp /bin
kris /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags"
kris *** Error code 1
kris Stop in /usr/src/bin/rcp.
kris *** Error code 1
kris ..
kris
krisOkay, you're a bad boy. Not because you got the error, but because you
krisdidn't read the other dozen or more messages which also talk about this
krisproblem and how to fix it. And you didn't read /usr/src/UPDATING, now, did
krisyou? You're really expected to do both of these things if you run
kris-current.
kris
krisKris

Regards,
  Listopad Alexandr
  ([EMAIL PROTECTED]), LAA7-RIPE
  ZGIA, Zaporozhye, Ukraine. 
  http://www.zgia.zp.ua. 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: help! need kernel!

[Alexandr Listopad]

cpiazzOn Wed, Jan 26, 2000 at 07:26:30PM +0200, Alexandr Listopad wrote:
cpiazz hello!
cpiazz 
cpiazz I have Abit motherboard with ATA-66 support.
cpiazz I try to install FreeBSD-CURRENT, all good when install, but after reboot
cpiazz kernel boots, but ask me a root device, when I press '?', there are no
cpiazz 'ad' device (this is my HDD). ;( As I understand - there are no support in
cpiazz that kernel for my HDD... ;(
cpiazz 
cpiazz As I understand there are one way to help me - create new kernel with
cpiazz ata-pci0 support.
cpiazz
cpiazzThe boot floppies have ATA in the kernel.  I installed a new system on 
cpiazza BP6 with the hard drive on one of the HPT366 controllers just fine
cpiazzabout two weeks ago.  Sorry, but I have no idea what is going on 
cpiazzhere.. I just wanted to say that it worked for me 
cpiazz
cpiazzata-pci1: HighPoint HPT366 ATA-66 controller port 0xd400-0xd4ff,0xd000-0xd003,
cpiazz0xcc00-0xcc07 irq 18 at device 19.0 on pci0
cpiazz...
cpiazzad4: 12949MB disk IBM-DJNA-371350 at ata2 as master mode UDMA66   
cpiazz
cpiazzBTW, sos, if you're reading this:  I like this format for reporting
cpiazzthe hard drives present a lot better :-).

All nice, in the install process...

My disk is ad4sXX in install, but after reboot it is ad0xxx - why?

Another questions in yesturdays cvsup I get full sources, but when I try
to make world make says:

/usr/src/tools/install.sh Can't open /usr/src/tools/install.sh
*** Error code 2

...


there no tools/ dir in /usr/src - why?

this is my supfile:

*default  host=cvsup2.ua.freebsd.org
*default  base=/usr/src-4.0
*default  prefix=/usr/src-4.0
*default  release=cvs
*default  tag=.
*default  delete use-rel-suffix

doc-all
src-base
src-bin
src-contrib
src-etc
src-gnu
src-include
src-lib
src-libexec
src-release
src-sbin
src-share
src-sys
src-usrbin
src-usrsbin


Thnaks.

Regards,
  Listopad Alexandr
  ([EMAIL PROTECTED]), LAA7-RIPE
  ZGIA, Zaporozhye, Ukraine. 
  http://www.zgia.zp.ua. 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

help! need kernel!

[Alexandr Listopad]

hello!

I have Abit motherboard with ATA-66 support.
I try to install FreeBSD-CURRENT, all good when install, but after reboot
kernel boots, but ask me a root device, when I press '?', there are no
'ad' device (this is my HDD). ;( As I understand - there are no support in
that kernel for my HDD... ;(

As I understand there are one way to help me - create new kernel with
ata-pci0 support.

If somebody can help me - please help!

Thanks!

P.S. I have latest cvs tree (but on the 3.4 box) and have latest kern.flp
and mfsroot.flp.


Regards,
  Listopad Alexandr
  ([EMAIL PROTECTED]), LAA7-RIPE
  ZGIA, Zaporozhye, Ukraine. 
  http://www.zgia.zp.ua. 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: help! need kernel!

[Alexandr Listopad]

cpiazz hello!
cpiazz 
cpiazz I have Abit motherboard with ATA-66 support.
cpiazz I try to install FreeBSD-CURRENT, all good when install, but after reboot
cpiazz kernel boots, but ask me a root device, when I press '?', there are no
cpiazz 'ad' device (this is my HDD). ;( As I understand - there are no support in
cpiazz that kernel for my HDD... ;(
cpiazz 
cpiazz As I understand there are one way to help me - create new kernel with
cpiazz ata-pci0 support.

Thanks you for your answer!

cpiazz
cpiazzThe boot floppies have ATA in the kernel.  I installed a new system on 
cpiazza BP6 with the hard drive on one of the HPT366 controllers just fine
cpiazzabout two weeks ago.  Sorry, but I have no idea what is going on 
cpiazzhere.. I just wanted to say that it worked for me 

I had installed FreeBSD-CURRENT on my PC, from flopppies and ftp, all ok.
But after reboot and press F3 new kernel boots (!) and after test wd0 and
some other devices (no ata-pci) ask me: from what partition we will boot?

My root partition is ad4s3a, but its don't work... ;

I have a question - where from the kernel boots? ;) And why it don't work
on ad4s3a

cpiazz
cpiazzata-pci1: HighPoint HPT366 ATA-66 controller port 0xd400-0xd4ff,0xd000-0xd003,
cpiazz0xcc00-0xcc07 irq 18 at device 19.0 on pci0
cpiazz...
cpiazzad4: 12949MB disk IBM-DJNA-371350 at ata2 as master mode UDMA66   
cpiazz
cpiazzBTW, sos, if you're reading this:  I like this format for reporting
cpiazzthe hard drives present a lot better :-).
cpiazz

What is your HPT-366 (Abit BE6) BIOS ver?

Thanks.

Regards,
  Listopad Alexandr
  ([EMAIL PROTECTED]), LAA7-RIPE
  ZGIA, Zaporozhye, Ukraine. 
  http://www.zgia.zp.ua. 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

making release

[Alexandr Listopad]

Hi.

I want to make a release of 4.0-CUR in 3.4-ST. Will it nice idea? Now I
cvsuping sources of 4.0. Is there any troubles?

And another one question: I don't cvsup "cvs-crypto". Will my release
maked?

Thanks. ..and sorry for my bad English. ;|

P.S. pls reply to me, i'm not currently subscribed.

Regards,
  Listopad Alexandr
  ([EMAIL PROTECTED]), LAA7-RIPE
  ZGIA, Zaporozhye, Ukraine. 
  http://www.zgia.zp.ua. 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

RE: gcc

[alexandr]

In Reply to Your Message of Sun, 28 Feb 1999 20: 38:49 -0400
Date: Sun, 28 Feb 1999 22:08:14 -0500
From: Jerry Alexandratos alexa...@mail.eecis.udel.edu
Message-ID:  199902282208.aa04...@mail.eecis.udel.edu

The Hermit Hacker scra...@hub.org says:
: On Sun, 28 Feb 1999, Chuck Robey wrote:
: 
:  Your argument about CS students needing the better compiler was true,
:  but totally ignored the fact that getting the CS students their compiler
:  IS NOT the top priority, especially since ports can do it (did for me).
: 
: U, you mis-quoted.  I agree with your above, and my statement had to
: do with an inability of FreeBSD to run on the hardware that we have (IBM
: thinkpad laptops) then anything software related (other then
: kernel/driver)...

I think I take offense to this statement.  I've been running FreeBSD on
various models of StinkPads for the past two+ years.  The combo works
(mostly) like a charm too.

   --Jerry

8) Jerry Alexandratos  % - %   Nothing inhabits my(8 
8) alexa...@louie.udel.edu % - %thoughts, and oblivion (8
8) darks...@strauss.udel.edu   % - %drives my desires.(8


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message