Re: Can't run `make universe` on universe11a.freebsd.org and ref11-amd64.freebsd.org (anymore); [shell] globbing is broken [there]

2016-02-10 Thread Dimitry Andric 
On 10 Feb 2016, at 01:03, Adrian Chadd  wrote:
> 
> Ok, so this has been broken since at least early January, right?
> 
> Firstly - how do I get around it? ok, it looks like env LANG=C gets around it.
> 
> Secondly - why hasn't this been fixed in -HEAD? Does this mean that
> noone has been doing universe builds since this happened?

I have ran more than a handful of universe builds, but I simply use LANG=C.

-Dimitry



signature.asc
Description: Message signed with OpenPGP using GPGMail

Jenkins build is back to stable : FreeBSD_HEAD #156

2016-02-10 Thread jenkins-admin 
See 

___
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: Can't run `make universe` on universe11a.freebsd.org and ref11-amd64.freebsd.org (anymore); [shell] globbing is broken [there]

2016-02-10 Thread Adrian Chadd 
I see it was recently fixed in -HEAD. I'll try it again (without
LANG=C) this afternoon.

Thanks!


-a


On 10 February 2016 at 06:17, Dimitry Andric  wrote:
> On 10 Feb 2016, at 01:03, Adrian Chadd  wrote:
>>
>> Ok, so this has been broken since at least early January, right?
>>
>> Firstly - how do I get around it? ok, it looks like env LANG=C gets around 
>> it.
>>
>> Secondly - why hasn't this been fixed in -HEAD? Does this mean that
>> noone has been doing universe builds since this happened?
>
> I have ran more than a handful of universe builds, but I simply use LANG=C.
>
> -Dimitry
>
___
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"

Memory modified after free in "MAP ENTRY" zone (vm_map_entry_t->read_ahead)

2016-02-10 Thread Andriy Gapon 

Over a span of approximately 3 weeks I have got two slightly different panics of
the same kind.   The affected system is a several months old amd64 head.

 1 ===
Unread portion of the kernel message buffer:
panic: Memory modified after free 0xf8008c15ac80(128) val=adc0de @
0xf8008c15acdc

KDB: stack backtrace:
db_trace_self_wrapper() at 0x8041e90b = db_trace_self_wrapper+0x2b/frame
0xfe04f5349530
kdb_backtrace() at 0x80669a09 = kdb_backtrace+0x39/frame 
0xfe04f53495e0
vpanic() at 0x80634dec = vpanic+0x14c/frame 0xfe04f5349620
panic() at 0x80634b33 = panic+0x43/frame 0xfe04f5349680
trash_ctor() at 0x807de9c8 = trash_ctor+0x48/frame 0xfe04f5349690
uma_zalloc_arg() at 0x807da785 = uma_zalloc_arg+0x475/frame
0xfe04f5349720
uma_zalloc() at 0x807e44af = uma_zalloc+0xf/frame 0xfe04f5349730
vm_map_entry_create() at 0x807e5a2e = vm_map_entry_create+0x2e/frame
0xfe04f5349740
_vm_map_clip_start() at 0x807e69e3 = _vm_map_clip_start+0x123/frame
0xfe04f5349770
vm_map_wire() at 0x807e797d = vm_map_wire+0x11d/frame 0xfe04f53497f0
vslock() at 0x807e1a2b = vslock+0x6b/frame 0xfe04f5349810
sysctl_wire_old_buffer() at 0x8064148a =
sysctl_wire_old_buffer+0x4a/frame 0xfe04f5349830
sysctl_kern_proc() at 0x8062259b = sysctl_kern_proc+0x8b/frame
0xfe04f5349880
sysctl_root_handler_locked() at 0x80641a8e =
sysctl_root_handler_locked+0x8e/frame 0xfe04f53498c0
sysctl_root() at 0x806412fe = sysctl_root+0x13e/frame 0xfe04f5349940
userland_sysctl() at 0x8064183d = userland_sysctl+0x16d/frame
0xfe04f53499e0
sys___sysctl() at 0x80641694 = sys___sysctl+0x74/frame 
0xfe04f5349a90
syscallenter() at 0x8081fa20 = syscallenter+0x320/frame 
0xfe04f5349b00
amd64_syscall() at 0x8081f5ef = amd64_syscall+0x1f/frame 
0xfe04f5349bf0
Xfast_syscall() at 0x80807c5b = Xfast_syscall+0xfb/frame 
0xfe04f5349bf0
--- syscall (202, FreeBSD ELF64, sys___sysctl), rip = 0x8042225ea, rsp =
0x7fffcef8, rbp = 0x7fffcf30 ---
Uptime: 14d22h38m17s
==

 2 ===
Unread portion of the kernel message buffer:
panic: Memory modified after free 0xf80176692680(128) val=adc0de @
0xf801766926dc

KDB: stack backtrace:
db_trace_self_wrapper() at 0x8041e90b = db_trace_self_wrapper+0x2b/frame
0xfe04f507c5a0
kdb_backtrace() at 0x80669a09 = kdb_backtrace+0x39/frame 
0xfe04f507c650
vpanic() at 0x80634dec = vpanic+0x14c/frame 0xfe04f507c690
panic() at 0x80634b33 = panic+0x43/frame 0xfe04f507c6f0
trash_ctor() at 0x807de9c8 = trash_ctor+0x48/frame 0xfe04f507c700
uma_zalloc_arg() at 0x807da785 = uma_zalloc_arg+0x475/frame
0xfe04f507c790
uma_zalloc() at 0x807e44af = uma_zalloc+0xf/frame 0xfe04f507c7a0
vm_map_entry_create() at 0x807e5a2e = vm_map_entry_create+0x2e/frame
0xfe04f507c7b0
vm_map_insert() at 0x807e558a = vm_map_insert+0x2fa/frame 
0xfe04f507c850
vm_map_stack_locked() at 0x807e63cb = vm_map_stack_locked+0x13b/frame
0xfe04f507c8b0
vm_map_find() at 0x807e65d3 = vm_map_find+0x183/frame 0xfe04f507c950
vm_mmap_object() at 0x807eac99 = vm_mmap_object+0x329/frame
0xfe04f507c9d0
sys_mmap() at 0x807ea8ec = sys_mmap+0x41c/frame 0xfe04f507ca90
syscallenter() at 0x8081fa20 = syscallenter+0x320/frame 
0xfe04f507cb00
amd64_syscall() at 0x8081f5ef = amd64_syscall+0x1f/frame 
0xfe04f507cbf0
Xfast_syscall() at 0x80807c5b = Xfast_syscall+0xfb/frame 
0xfe04f507cbf0
--- syscall (477, FreeBSD ELF64, sys_mmap), rip = 0x80418776a, rsp =
0x7fffb808, rbp = 0x7fffb840 ---
Uptime: 4d4h36m36s
==

I have crash dumps from both panics.
It seems that it was read_ahead field that was reset to zero in both cases.
Perhaps the issue has been fixed already?
I would appreciate any suggestions. Thanks!

-- 
Andriy Gapon
___
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"

Jenkins build became unstable: FreeBSD_HEAD #157

2016-02-10 Thread jenkins-admin 
See 

___
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: Open Sound System - OSS "soundon" command causes KERNEL PANIC FreeBSD-11

2016-02-10 Thread Hans Petter Selasky 

On 02/11/16 03:02, Greg Quinlan wrote:

Hi HPS,
Note: Does not happen on FreeBSD 10.1-Stable!



Yes, that's because WITNESS is off in 10.x by default.

Does the attached patch solve your problem?

--HPS

Index: sys/kern/kern_module.c
===
--- sys/kern/kern_module.c	(revision 295464)
+++ sys/kern/kern_module.c	(working copy)
@@ -214,16 +214,24 @@
 module_lookupbyname(const char *name)
 {
 	module_t mod;
+	int xlocked;
 	int err;
 
-	MOD_LOCK_ASSERT;
-
+	/*
+	 * If the context is not properly locked, apply the proper
+	 * locks here:
+	 */
+	xlocked = sx_xlocked(_sx);
+	if (!xlocked)
+		MOD_SLOCK;
 	TAILQ_FOREACH(mod, , link) {
 		err = strcmp(mod->name, name);
 		if (err == 0)
-			return (mod);
+			break;
 	}
-	return (NULL);
+	if (!xlocked)
+		MOD_SUNLOCK;
+	return (mod);
 }
 
 module_t
___
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"

Open Sound System - OSS "soundon" command causes KERNEL PANIC FreeBSD-11

2016-02-10 Thread Greg Quinlan 
  
 Hi,

I haven't seen a Kernel Panic like this for a long time... i.e. repeatable and 
due to a single command.

I have compiled the port /usr/ports/audio/oss and installed it on FreeBSD11.

A ran  /usr/local/sbin/ossdetect which created the file 
/usr/local/lib/oss/etc/installed_drivers.

Contents:
Code:oss_hdaudio #Intel High Definition Audio (CPT)

When i run  /usr/local/sbin/soundon

The system panics..

Code:osscore.ac97_amplifier="0"
panic: Lock (sx) module subsystem lock sx lock not locked 0 
/usr/src/sys/kern/kern_module.c:219
cpu_id = 1
:


audio/oss Build 4.2-build2011

Any ideas?

I have taken out any reference to sound in a custom  kernel
# Sound support
#device  sound  # Generic sound driver (required)
#device  snd_cmi  # CMedia CMI8338/CMI8738
#device  snd_csa  # Crystal Semiconductor CS461x/428x
#device  snd_emu10kx  # Creative SoundBlaster Live! and Audigy
#device  snd_es137x  # Ensoniq AudioPCI ES137x
#device  snd_hda  # Intel High Definition Audio
#device  snd_ich  # Intel, NVidia and other ICH AC'97 Audio
#device  snd_via8233  # VIA VT8233x Audio


 # make buildkernel KERNCONF=GENERIC
 # make installkernel KERNCONF=GENERIC
Thanks 
 GQ
___
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: Open Sound System - OSS "soundon" command causes KERNEL PANIC FreeBSD-11

2016-02-10 Thread Hans Petter Selasky 

On 02/10/16 10:51, Greg Quinlan wrote:


  Hi,

I haven't seen a Kernel Panic like this for a long time... i.e. repeatable and 
due to a single command.

I have compiled the port /usr/ports/audio/oss and installed it on FreeBSD11.

A ran  /usr/local/sbin/ossdetect which created the file 
/usr/local/lib/oss/etc/installed_drivers.

Contents:
Code:oss_hdaudio #Intel High Definition Audio (CPT)

When i run  /usr/local/sbin/soundon

The system panics..

Code:osscore.ac97_amplifier="0"
panic: Lock (sx) module subsystem lock sx lock not locked 0 
/usr/src/sys/kern/kern_module.c:219
cpu_id = 1
:



Hi,

Do you have the complete backtrace for this panic?

Do you have any modules under /boot/modules, which are not up to date?

Does the same happen with audio/oss under 10.x ?

--HPS

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

Jenkins build became unstable: FreeBSD_HEAD #155

2016-02-10 Thread jenkins-admin 
See 

___
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: Panic on reloading a driver with same DEVICE_PROBE() return value

2016-02-10 Thread Sreekanth Reddy 
On Wed, Feb 10, 2016 at 3:30 AM, John Baldwin  wrote:
> On Tuesday, February 09, 2016 05:45:38 PM Sreekanth Reddy wrote:
>> Hi,
>>
>> While debugging more, I got one more clue,
>>
>> ---
>> static driver_t mps_pci_driver = {
>> "mpr",
>> mps_methods,
>> sizeof(struct mps_softc)
>> };
>>
>> static devclass_t   mps_devclass;
>> DRIVER_MODULE(mpr, pci, mps_pci_driver, mps_devclass, 0, 0);
>> -
>>
>> in the above code snip-set, if I changed "DRIVER_MODULE" line as
>> DRIVER_MODULE(mpr3, pci, mps_pci_driver, mps_devclass, 0, 0);
>> (i.e. from "mpr"  to "mpr3") then I am not observing any panic and I
>> can load & unload the mpr driver multiple times.
>
> Oh, that might be required, yes.  DRIVER_MODULE uses its arguments to define
> a module name (in this case as "pci/mpr") and module names are required to
> be unique.  I believe you should be getting a printf warning about this on
> the console.  Something like:
>
> "module_register: cannot register pci/mpr from blah.ko; already loaded from 
> foo.ko"

Yes, I am getting below messages, at OS boot time for Out-of-box driver

module_register: module pci/mpr already exists!
Module pci/mpr failed to register: 17

>
> --
> John Baldwin
___
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: pwcview and cheese - Device not configured / Invalid argument erros

2016-02-10 Thread Hans Petter Selasky 

On 02/10/16 11:27, miguelmcl...@gmail.com wrote:

Running the latest ports version for webcamd and cuse4bsd kmod ATM.

I haven't used it for a while and since I upgrade pkgs frequently I'm guessing 
yes but, I've also updated current kernel/userland a few times for the last 
time this worked and all I can remember it was at least in 2015 so its hard to 
tell what caused the regression.



Hi,

pwcview doesn't work either?

Did you try different resolutions with pwcview?

--HPS

___
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: pwcview and cheese - Device not configured / Invalid argument erros

2016-02-10 Thread miguelmclara 
Running the latest ports version for webcamd and cuse4bsd kmod ATM.

I haven't used it for a while and since I upgrade pkgs frequently I'm guessing 
yes but, I've also updated current kernel/userland a few times for the last 
time this worked and all I can remember it was at least in 2015 so its hard to 
tell what caused the regression.


On 10 February 2016 06:40:06 WET, Hans Petter Selasky  wrote:
>On 02/09/16 21:22, Miguel C wrote:
>> I while ago cheese was working fine but I was just playing around
>with my
>> webcam today and noticed that I get this error with cheese:
>>
>> 'libv4l2: error turning on stream: Device not configured'
>
>What version of webcamd are you running?
>
>Did you upgrade since last time?
>
>--HPS

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
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: Open Sound System - OSS "soundon" command causes KERNEL PANIC FreeBSD-11

2016-02-10 Thread Konstantin Belousov 
On Wed, Feb 10, 2016 at 09:51:01AM +, Greg Quinlan wrote:
>   
>  Hi,
> 
> I haven't seen a Kernel Panic like this for a long time... i.e. repeatable 
> and due to a single command.
> 
> I have compiled the port /usr/ports/audio/oss and installed it on FreeBSD11.
> 
> A ran  /usr/local/sbin/ossdetect which created the file 
> /usr/local/lib/oss/etc/installed_drivers.
> 
> Contents:
> Code:oss_hdaudio #Intel High Definition Audio (CPT)
> 
> When i run  /usr/local/sbin/soundon
> 
> The system panics..
> 
> Code:osscore.ac97_amplifier="0"
> panic: Lock (sx) module subsystem lock sx lock not locked 0 
> /usr/src/sys/kern/kern_module.c:219
> cpu_id = 1
> :
> 
> 
> audio/oss Build 4.2-build2011
> 
> Any ideas?
Show the backtrace.  Basically, the information that you have stripped
from your mail.
___
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"

IPV6 TCP6 Slow Connect

2016-02-10 Thread Larry Rosenman 

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

I've also posted lots of info to freebsd-net, and not gotten any 
response.


Summary:

Cable Modem-> EM0 on a pfSense Firewall (FreeBSD 10.1, pfSense 2.2.6)
  set to dhcp6, and ask for a /56 prefix

EM1->LAN, set to track interface, prefix id 0, radvd running advertising 
the 00 /64
LAN-> borg.lerctr.org using lagg0, SLAAC (rtsold).  Gets an address, 
icmp6 works, tcp6 times out.

-> win10 SLAAC, tcp6 works fine, as does icmp6.

I seem to be able to CRASH -CURRENT by just rebooting the pfSense 
firewall.


What do I need to get to help get to the bottom of this?



--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961
___
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"

Jenkins build is back to stable : FreeBSD_HEAD #158

2016-02-10 Thread jenkins-admin 
See 

___
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: Open Sound System - OSS "soundon" command causes KERNEL PANIC FreeBSD-11

2016-02-10 Thread Greg Quinlan 
Hi HPS,
Note: Does not happen on FreeBSD 10.1-Stable!

Complete back trace:
panic: Lock (sx) module subsystem sx lock not locked @ 
/usr/src/sys/kern/kern_module.c:219.
cpuid = 0
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe02376ae530
vpanic() at vpanic+0x182/frame 0xdbfe02376ae5b0
kassert_panic at kasset_panic+0x126/frame 0xfe02376ae620
witness_assert() at wintness_assert+0x346/frame 0xfe02376ae680
module_lookupbyname() atm odule_lookupbyname+0x2a/frame 0xfe02376ae6b0
soundcard_attach() at soundcard_attach+0x12/frame 0xfe023766d0
module_rgister_init() at module_rgister_init+0xb0/frame 0xfe02376ae700
linker_load_module() at linker_load_module+0xc8e/frame 0xfe02376aea30
kern_kldload() at sys_kldload+0xa7/frame 0xfe02376aea70
sys_kldload() at sys_kldload+0x5b/frame 0xfe02376aeaa0
amd64_syscall() at amd64_syscall+02db/frame 0xfe02376aebb0
xfast_syscall() at xfast_syscall+0fb/frame 0xfe02376aebb0
--- syscall (304, FreeBSD ELF64, sys_kldload, rip = 0x80086b6aa, rsp = 
0x7fffe718, rbp = 0x7fffec30 ---
KDB: enter: panic
[ thread pid 1025 tid 100233 ]
Stopped at  kdb_enter+0x3b: movq    $0,kdb_why
/boot/modules
# cd /boot/modules
# ls -ltr
total 15008
-r-xr-xr-x  1 root  wheel  80280  Nov  6  15:01 fuse.ko
-r-xr-xr-x  1 root  wheel  1633464  Nov  6  15:02 radeonkms_port.ko
-r-xr-xr-x  1 root  wheel    700232  Nov  6  15:02 i915kms_port.ko
-r-xr-xr-x  1 root  wheel    421696  Nov  6  15:02 drm2_port.ko
-r-xr-xr-x  1 root  wheel  26848  Dec 15 21:39 vboxnetflt.ko
-r-xr-xr-x  1 root  wheel    9752  Dec 15 21:39 vboxnetadp.ko
-r-xr-xr-x  1 root  wheel    356152  Dec 15 21:39 vboxdrv.ko
-r-xr-xr-x  1 root  wheel      38632  Dec 16 07:05 cuse4bsd.ko
-r-xr-xr-x  1 root  wheel 11926368 Dec 20 07:40 nvidia.ko
-rw-r--r--  1 root  wheel         1008 Dec 20 07:40 linker.hints

Thanks GQ
  From: Hans Petter Selasky 
 To: Greg Quinlan ; "freebsd-current@freebsd.org" 
 
 Sent: Wednesday, 10 February 2016, 21:07
 Subject: Re: Open Sound System - OSS "soundon" command causes KERNEL PANIC 
FreeBSD-11
   
On 02/10/16 10:51, Greg Quinlan wrote:
>
>  Hi,
>
> I haven't seen a Kernel Panic like this for a long time... i.e. repeatable 
> and due to a single command.
>
> I have compiled the port /usr/ports/audio/oss and installed it on FreeBSD11.
>
> A ran  /usr/local/sbin/ossdetect which created the file 
> /usr/local/lib/oss/etc/installed_drivers.
>
> Contents:
> Code:oss_hdaudio #Intel High Definition Audio (CPT)
>
> When i run  /usr/local/sbin/soundon
>
> The system panics..
>
> Code:osscore.ac97_amplifier="0"
> panic: Lock (sx) module subsystem lock sx lock not locked 0 
> /usr/src/sys/kern/kern_module.c:219
> cpu_id = 1
> :
>

Hi,

Do you have the complete backtrace for this panic?

Do you have any modules under /boot/modules, which are not up to date?

Does the same happen with audio/oss under 10.x ?

--HPS



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