Re: Troubles with VIA VX900 chipset

2013-10-24 Thread Alexander Motin
Hi. On 24.10.2013 16:56, Alexandre Martins wrote: We have seen some issues with the VIA VX900 chipset. The main trouble is that some SATA hard drive are not seen by the kernel (BIOS and boot-loader are OK). After investigations, it seems that during the initialisation of the controler, some res

[head tinderbox] failure on i386/pc98

2013-10-24 Thread FreeBSD Tinderbox
TB --- 2013-10-25 06:23:13 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-10-25 06:23:13 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013

Re: ZFS L2ARC - incorrect size and abnormal system load on r255173

2013-10-24 Thread Vitalij Satanivskij
Hello Bad news, to day two servers with applayed patches get L2ARC degraded L2 ARC Summary: (DEGRADED) Passed Headroom:4.17m Tried Lock Failures:635.53m IO In Progress: 41.89k Low Memory Aborts:

Re: gperf/src/options.cc -- quiesce clang warnings -Wlogical-op-parentheses

2013-10-24 Thread Sean Bruno
On Thu, 2013-10-24 at 21:24 -0400, David Chisnall wrote: > > Don't forget the freelocale() at the end. > ah, ok. I wish that there was some kind of example that I could go off of in the man page. I'm sort of trundling my way through various bits of the system to find the obvious example of how

Re: gperf/src/options.cc -- quiesce clang warnings -Wlogical-op-parentheses

2013-10-24 Thread David Chisnall
On 24 Oct 2013, at 21:13, Sean Bruno wrote: > On Tue, 2013-10-22 at 09:47 +0100, David Chisnall wrote: >> On 22 Oct 2013, at 00:43, Sean Bruno wrote: >> >>> Heh, Matthew suggested the obvious in private mail, it seems that this >>> would be better "spelled" as "isalpha" :-) >> >> This looks w

Re: gperf/src/options.cc -- quiesce clang warnings -Wlogical-op-parentheses

2013-10-24 Thread Sean Bruno
On Tue, 2013-10-22 at 09:47 +0100, David Chisnall wrote: > On 22 Oct 2013, at 00:43, Sean Bruno wrote: > > > Heh, Matthew suggested the obvious in private mail, it seems that this > > would be better "spelled" as "isalpha" :-) > > This looks wrong. The behaviour of isalpha() depends on the curr

Re: CUREENT issue with ballon.c

2013-10-24 Thread Outback Dingo
On Thu, Oct 24, 2013 at 6:24 PM, Outback Dingo wrote: > > > > On Thu, Oct 24, 2013 at 6:17 PM, Roger Pau Monné wrote: > >> On 24/10/13 22:15, Konstantin Belousov wrote: >> > On Thu, Oct 24, 2013 at 09:45:20PM +0100, Roger Pau Monn? wrote: >> >> On 24/10/13 13:01, Outback Dingo wrote: >> >>> >> >>>

Re: CUREENT issue with ballon.c

2013-10-24 Thread Outback Dingo
On Thu, Oct 24, 2013 at 6:17 PM, Roger Pau Monné wrote: > On 24/10/13 22:15, Konstantin Belousov wrote: > > On Thu, Oct 24, 2013 at 09:45:20PM +0100, Roger Pau Monn? wrote: > >> On 24/10/13 13:01, Outback Dingo wrote: > >>> > >>> > >>> On Thu, Oct 24, 2013 at 6:16 AM, Roger Pau Monn? >>>

Re: 10.0-BETA1 i386 on VirtualBox

2013-10-24 Thread Maciej Milewski
On 24.10.2013 17:47, Maciej Milewski wrote: On 24.10.2013 17:34, Ryan Stone wrote: On Thu, Oct 24, 2013 at 11:16 AM, Maciej Milewski wrote: I've encountered problems with installing FreeBSD-10.0-BETA1 i386 under VirtualBox. The problem is with setting/changing root password during install pro

Re: CUREENT issue with ballon.c

2013-10-24 Thread Roger Pau Monné
On 24/10/13 22:15, Konstantin Belousov wrote: > On Thu, Oct 24, 2013 at 09:45:20PM +0100, Roger Pau Monn? wrote: >> On 24/10/13 13:01, Outback Dingo wrote: >>> >>> >>> On Thu, Oct 24, 2013 at 6:16 AM, Roger Pau Monn? >> > wrote: >>> >>> On 24/10/13 03:02, Outback Di

Re: CUREENT issue with ballon.c

2013-10-24 Thread Konstantin Belousov
On Thu, Oct 24, 2013 at 09:45:20PM +0100, Roger Pau Monn? wrote: > On 24/10/13 13:01, Outback Dingo wrote: > > > > > > On Thu, Oct 24, 2013 at 6:16 AM, Roger Pau Monn? > > wrote: > > > > On 24/10/13 03:02, Outback Dingo wrote: > > > --- trap 0, rip = 0, rsp

Re: CUREENT issue with ballon.c

2013-10-24 Thread Roger Pau Monné
On 24/10/13 13:01, Outback Dingo wrote: > > > On Thu, Oct 24, 2013 at 6:16 AM, Roger Pau Monné > wrote: > > On 24/10/13 03:02, Outback Dingo wrote: > > --- trap 0, rip = 0, rsp = 0xfe2c6b70, rbp = 0 --- > > uma_zalloc_arg: zone "16" with the foll

[head tinderbox] failure on i386/pc98

2013-10-24 Thread FreeBSD Tinderbox
TB --- 2013-10-24 19:13:12 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-10-24 19:13:12 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013

Re: Troubles with VIA VX900 chipset

2013-10-24 Thread Adrian Chadd
Hi! Would you please create a PR with the patches attached? That way it's not lost. Thanks! -a On 24 October 2013 06:56, Alexandre Martins wrote: > Dear, > > We have seen some issues with the VIA VX900 chipset. The main trouble is > that > some SATA hard drive are not seen by the kernel (BI

Re: 10.0-BETA1 i386 on VirtualBox

2013-10-24 Thread Maciej Milewski
On 24.10.2013 17:34, Ryan Stone wrote: On Thu, Oct 24, 2013 at 11:16 AM, Maciej Milewski wrote: I've encountered problems with installing FreeBSD-10.0-BETA1 i386 under VirtualBox. The problem is with setting/changing root password during install process. After entering password twice there is:

Re: 10.0-BETA1 i386 on VirtualBox

2013-10-24 Thread Ryan Stone
On Thu, Oct 24, 2013 at 11:16 AM, Maciej Milewski wrote: > I've encountered problems with installing FreeBSD-10.0-BETA1 i386 under > VirtualBox. > The problem is with setting/changing root password during install process. > After entering password twice there is: > > passwd: pam_chauthtok(): error

10.0-BETA1 i386 on VirtualBox

2013-10-24 Thread Maciej Milewski
I've encountered problems with installing FreeBSD-10.0-BETA1 i386 under VirtualBox. The problem is with setting/changing root password during install process. After entering password twice there is: passwd: pam_chauthtok(): error in service module Then there shows pwd_mkdb.core in current dire

Re: Troubles with VIA VX900 chipset

2013-10-24 Thread Alexandre Martins
I forget to attach patches Le jeudi 24 octobre 2013 15:56:15 Alexandre Martins a écrit : > Dear, > > We have seen some issues with the VIA VX900 chipset. The main trouble is > that some SATA hard drive are not seen by the kernel (BIOS and boot-loader > are OK). > > After investigations, it seems

Troubles with VIA VX900 chipset

2013-10-24 Thread Alexandre Martins
Dear, We have seen some issues with the VIA VX900 chipset. The main trouble is that some SATA hard drive are not seen by the kernel (BIOS and boot-loader are OK). After investigations, it seems that during the initialisation of the controler, some reset commands are send via "ata_via_sata_reset

Re: CUREENT issue with ballon.c

2013-10-24 Thread Outback Dingo
On Thu, Oct 24, 2013 at 6:16 AM, Roger Pau Monné wrote: > On 24/10/13 03:02, Outback Dingo wrote: > > --- trap 0, rip = 0, rsp = 0xfe2c6b70, rbp = 0 --- > > uma_zalloc_arg: zone "16" with the following non-sleepable locks held: > > exclusive sleep mutex balloon_lock (balloon_lock) r = 0 >

Re: [CAM] panic / general protection fault while in kernel mode on head r256931

2013-10-24 Thread Bryan Drewery
On 10/23/2013 8:14 AM, Alexander Motin wrote: > On 23.10.2013 14:22, Bryan Drewery wrote: >> On 10/23/2013 1:59 AM, Alexander Motin wrote: >>> Unfortunately I have never seen that, but I'll try to look harder. Could >>> you please tell a bit about your controllers/devices? What triggered the >>> is

some experience with a many core machine: event timer, hwpmc

2013-10-24 Thread Andriy Gapon
I don't think that I have seen observations like the following posted before. I had some brief contact with a 48 core Opteron system (4 packages). Observation #1. Event timers subsystem picked a HPET timer as its source. This resulted in a lot of inter-core / inter-package traffic to re-distri

Re: CUREENT issue with ballon.c

2013-10-24 Thread Roger Pau Monné
On 24/10/13 03:02, Outback Dingo wrote: > --- trap 0, rip = 0, rsp = 0xfe2c6b70, rbp = 0 --- > uma_zalloc_arg: zone "16" with the following non-sleepable locks held: > exclusive sleep mutex balloon_lock (balloon_lock) r = 0 > (0x816e9c58) locked @ /usr/src/sys/dev/xen/balloon/balloo

Re: deadlkres: possible deadlock detected for 0xe000000012aed200, blocked for 900014 ticks

2013-10-24 Thread Anton Shterenlikht
>From j...@freebsd.org Wed Oct 23 21:10:30 2013 >> >> >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/183007 >> > >> >Hmm, unfortunately it seems like all the stack traces did not work. There >are >> >lots of threads blocked on VM-related locks, and CPU 0 is running >vm_daemon. >> >Proba

Re: [rfc] removing the NDISulator

2013-10-24 Thread Maciej Milewski
On 24.10.2013 05:46, Thomas Mueller wrote: I have motherboard (MSI Z77 MPOWER) with Realtek 8111E Ethernet that fails to connect in FreeBSD or OpenBSD, OK with NetBSD-current and Linux, and Atheros AR9271 onboard wifi: device athn is included in NetBSD (current only) and OpenBSD. Tom For your pr

[head tinderbox] failure on i386/pc98

2013-10-24 Thread FreeBSD Tinderbox
TB --- 2013-10-24 07:57:22 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-10-24 07:57:22 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013