Fatal double fault in ZFS with yesterday's CURRENT

2014-05-03 Thread Fabian Keil
After updating my laptop to yesterday's CURRENT (r265216), I got the following fatal double fault on boot: http://www.fabiankeil.de/bilder/freebsd/kernel-panic-r265216/ My previous kernel was based on r264721. I'm using a couple of custom patches, some of them are ZFS-related and thus may be part

need info about newcons in jails

2014-05-03 Thread Fbsd8
Hello list. Looking for information about using newcons as the terminal driver in xorg for desktop in a jail. Can only find this https://wiki.freebsd.org/Newcons Has anybody gotten it to work in a jail? Thanks ___ freebsd-current@freebsd.org mailin

Re: Fatal double fault in ZFS with yesterday's CURRENT

2014-05-03 Thread Steven Hartland
- Original Message - From: "Fabian Keil" After updating my laptop to yesterday's CURRENT (r265216), I got the following fatal double fault on boot: http://www.fabiankeil.de/bilder/freebsd/kernel-panic-r265216/ My previous kernel was based on r264721. I'm using a couple of custom patc

[arm, zfs] zpool create: zap->zap_rwlock

2014-05-03 Thread Boris Samorodov
Hi All, The system: - FreeBSD 11.0-CURRENT #6 r265218M: Fri May 2 18:24:07 SAMT 2014 bsam@wandboard:/usr/obj/usr/src/sys/WANDBOARD-QUAD arm FreeBSD clang version 3.4 (tags/RELEASE_34/final 197956) 20140216 CPU: Cortex A9-r2 rev 10 (Cortex-A core) Supported features: ARM_ISA THUMB2 JAZELL

Re: Leaving the Desktop Market

2014-05-03 Thread Matthias Apitz
El día Tuesday, April 01, 2014 a las 08:38:28AM +0100, David Chisnall escribió: > > Just a small note here: Improving power management is something that the Core > Team and the Foundation have jointly identified as an important goal, in > particular for mobile / embedded scenarios. We're curre

Re: Leaving the Desktop Market

2014-05-03 Thread Adrian Chadd
Hi, I'm working on adding some more power management logging support to freebsd-head so we can start to get a better grip on sleep/wakeup occurances. That should help us start to figure out where the power consumption is going. But on that EEEPC 900, just make sure you've set dev.cpu.0.cx_lowest

Re: Fatal double fault in ZFS with yesterday's CURRENT

2014-05-03 Thread Fabian Keil
"Steven Hartland" wrote: > From: "Fabian Keil" > > > After updating my laptop to yesterday's CURRENT (r265216), > > I got the following fatal double fault on boot: > > http://www.fabiankeil.de/bilder/freebsd/kernel-panic-r265216/ > > > > My previous kernel was based on r264721. > > > > I'm usi

Re: Fatal double fault in ZFS with yesterday's CURRENT

2014-05-03 Thread Steven Hartland
"Steven Hartland" wrote: > From: "Fabian Keil" > > > After updating my laptop to yesterday's CURRENT (r265216), > > I got the following fatal double fault on boot: > > http://www.fabiankeil.de/bilder/freebsd/kernel-panic-r265216/ > > > > My previous kernel was based on r264721. > > > > I'm

Re: Leaving the Desktop Market

2014-05-03 Thread Matthias Apitz
El día Saturday, May 03, 2014 a las 09:37:08AM -0700, Adrian Chadd escribió: > Hi, > > I'm working on adding some more power management logging support to > freebsd-head so we can start to get a better grip on sleep/wakeup > occurances. That should help us start to figure out where the power > co

r265279 causes gpf at sys/net/route.c:930

2014-05-03 Thread Trond Endrestøl
Hi, I updated one of my amd64 base/head VMs this afternoon. It crashes in rt_expunge(), and I think r265279 is to blame. If someone's interested, here's the crash report: http://ximalas.info/~trond/amd64-head-VBOX-crash/r265283/core.txt.0 Another amd64 base/head VM I updated earlier this aftern

Re: r265279 causes gpf at sys/net/route.c:930

2014-05-03 Thread Alexander V. Chernikov
On 04.05.2014 00:02, Trond Endrestøl wrote: > Hi, > > I updated one of my amd64 base/head VMs this afternoon. > It crashes in rt_expunge(), and I think r265279 is to blame. > > If someone's interested, here's the crash report: > > http://ximalas.info/~trond/amd64-head-VBOX-crash/r265283/core.txt

Re: r265279 causes gpf at sys/net/route.c:930

2014-05-03 Thread Alexander V. Chernikov
On 04.05.2014 00:06, Alexander V. Chernikov wrote: > On 04.05.2014 00:02, Trond Endrestøl wrote: >> Hi, >> >> I updated one of my amd64 base/head VMs this afternoon. >> It crashes in rt_expunge(), and I think r265279 is to blame. >> >> If someone's interested, here's the crash report: >> >> http://

Re: Leaving the Desktop Market

2014-05-03 Thread Adrian Chadd
Set it to the lowest available Cx state that you see in dev.cpu.0 . -a On 3 May 2014 12:23, Matthias Apitz wrote: > El día Saturday, May 03, 2014 a las 09:37:08AM -0700, Adrian Chadd escribió: > >> Hi, >> >> I'm working on adding some more power management logging support to >> freebsd-head so

Re: Leaving the Desktop Market

2014-05-03 Thread Kevin Oberman
On Sat, May 3, 2014 at 1:25 PM, Adrian Chadd wrote: > Set it to the lowest available Cx state that you see in dev.cpu.0 . > > Available is not required. Set it to C8. That guarantees that you will use the lowest available. The correct incantation in rc.conf is "Cmax". performance_cx_lowest="Cmax"

Re: Leaving the Desktop Market

2014-05-03 Thread Nathan Whitehorn
On 05/03/14 16:59, Kevin Oberman wrote: On Sat, May 3, 2014 at 1:25 PM, Adrian Chadd wrote: Set it to the lowest available Cx state that you see in dev.cpu.0 . Available is not required. Set it to C8. That guarantees that you will use the lowest available. The correct incantation in rc.conf

Re: Leaving the Desktop Market

2014-05-03 Thread Adrian Chadd
TCC is fine. TCC for doing anything other than _thermal throttling_ these days isn't. I've been kind of trying hard to avoid touching it as I'm worried it'll stick to me, but something tells me i'm just going to have to bite the bullet and grab ownership of this stuff... :( -a On 3 May 2014

Re: Leaving the Desktop Market

2014-05-03 Thread Kevin Oberman
On Sat, May 3, 2014 at 6:07 PM, Nathan Whitehorn wrote: > On 05/03/14 16:59, Kevin Oberman wrote: > >> On Sat, May 3, 2014 at 1:25 PM, Adrian Chadd wrote: >> >> Set it to the lowest available Cx state that you see in dev.cpu.0 . >>> >>> >>> Available is not required. Set it to C8. That guarante

Re: Leaving the Desktop Market

2014-05-03 Thread Adrian Chadd
Hi, Well, hardware got better. A lot better. I'm happy to leave speedstep and throttling in there but teach powerd about using C-states and limited frequency stepping if it's available. So, how about something like this: * if C states are available - let's just use C states and not step the cpu

Re: Leaving the Desktop Market

2014-05-03 Thread Allan Jude
On 2014-05-04 00:49, Adrian Chadd wrote: > Hi, > > Well, hardware got better. A lot better. I'm happy to leave speedstep > and throttling in there but teach powerd about using C-states and > limited frequency stepping if it's available. > > So, how about something like this: > > * if C states ar

Re: Leaving the Desktop Market

2014-05-03 Thread Adrian Chadd
On 3 May 2014 21:52, Allan Jude wrote: > On 2014-05-04 00:49, Adrian Chadd wrote: >> Hi, >> >> Well, hardware got better. A lot better. I'm happy to leave speedstep >> and throttling in there but teach powerd about using C-states and >> limited frequency stepping if it's available. >> >> So, how a

Re: Leaving the Desktop Market

2014-05-03 Thread Kevin Oberman
On Sat, May 3, 2014 at 9:49 PM, Adrian Chadd wrote: > Hi, > > Well, hardware got better. A lot better. I'm happy to leave speedstep > and throttling in there but teach powerd about using C-states and > limited frequency stepping if it's available. > > So, how about something like this: > > * if C