(more) screen distortion with intel GPU / xorg on recent -HEAD?

2014-03-23 Thread Adrian Chadd
Hi,

I know this is an information-poor message.

The last time i updated my two test laptops was around the middle of
last month. Back then, xorg would occasionally get distorted, but
typically would come back from suspend fine.

Lately, it seems a 50% chance that coming back from suspend that xorg
will be not only distorted, but further screen redraws are wrong. It's
like the framebuffer configuration is wrong and persists to be wrong.
I have to exit out of xorg and restart it.

Has anyone else seen this?


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


Unable to build kernel #263665 config: illegal option -- I

2014-03-23 Thread Vladimir Sharun
Hello FreeBSD comunity,

Got yesterday following issue with #263665:

# make kernel


--
 Kernel build for COBALT started on Sun Mar 23 17:44:45 EET 2014
--
=== COBALT
mkdir -p /usr/obj/usr/src/sys


--
 stage 1: configuring the kernel
--
cd /usr/src/sys/amd64/conf;  
PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/legacy/bin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
  config  -d /usr/obj/usr/src/sys/COBALT  -I /usr/src/sys/amd64/conf 
/usr/src/sys/amd64/conf/COBALT
config: illegal option -- I
usage: config [-CgmpV] [-d destdir] sysname
       config -x kernel
*** Error code 64


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


Stop.
make: stopped in /usr/src

The same for GENERIC as well. Emptying src.conf and make.conf doesn't help.
Last kernel succesfully built (the system now runs it) was r263345

___
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: Unable to build kernel #263665 config: illegal option -- I

2014-03-23 Thread Milan Obuch
On Sun, 23 Mar 2014 17:52:40 +0200
Vladimir Sharun a...@ukr.net wrote:

 Hello FreeBSD comunity,
 
 Got yesterday following issue with #263665:
 
 # make kernel
 
 
 --
  Kernel build for COBALT started on Sun Mar 23 17:44:45 EET 2014
 --
 === COBALT
 mkdir -p /usr/obj/usr/src/sys
 
 
 --
  stage 1: configuring the kernel
 --
 cd /usr/src/sys/amd64/conf;
  
 PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/legacy/bin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
  config  -d /usr/obj/usr/src/sys/COBALT
  -I /usr/src/sys/amd64/conf /usr/src/sys/amd64/conf/COBALT config:
 illegal option -- I usage: config [-CgmpV] [-d destdir] sysname
 config -x kernel *** Error code 64
 
 
 Stop.
 make[1]: stopped in /usr/src
 *** Error code 1
 
 
 Stop.
 make: stopped in /usr/src
 
 The same for GENERIC as well. Emptying src.conf and make.conf doesn't
 help. Last kernel succesfully built (the system now runs it) was
 r263345
 

Hi,

did see this (or something similar) too. Cured with 'make
kernel-toolchain' and only then 'make buildkernel'. Could you try tis?

Regards,
Milan
___
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[2]: Unable to build kernel #263665 config: illegal option -- I

2014-03-23 Thread Vladimir Sharun
Hello Milan,

This solution (make toolchain first) cure the problem.

Thank you.


 did see this (or something similar) too. Cured with 'make
 kernel-toolchain' and only then 'make buildkernel'. Could you try tis?
___
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: Unable to build kernel #263665 config: illegal option -- I

2014-03-23 Thread Warner Losh

On Mar 23, 2014, at 10:06 AM, Milan Obuch freebsd-curr...@dino.sk wrote:

 On Sun, 23 Mar 2014 17:52:40 +0200
 Vladimir Sharun a...@ukr.net wrote:
 
 Hello FreeBSD comunity,
 
 Got yesterday following issue with #263665:
 
 # make kernel
 
 
 --
 Kernel build for COBALT started on Sun Mar 23 17:44:45 EET 2014
 --
 === COBALT
 mkdir -p /usr/obj/usr/src/sys
 
 
 --
 stage 1: configuring the kernel
 --
 cd /usr/src/sys/amd64/conf;
  
 PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/legacy/bin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
  config  -d /usr/obj/usr/src/sys/COBALT
  -I /usr/src/sys/amd64/conf /usr/src/sys/amd64/conf/COBALT config:
 illegal option -- I usage: config [-CgmpV] [-d destdir] sysname
 config -x kernel *** Error code 64
 
 
 Stop.
 make[1]: stopped in /usr/src
 *** Error code 1
 
 
 Stop.
 make: stopped in /usr/src
 
 The same for GENERIC as well. Emptying src.conf and make.conf doesn't
 help. Last kernel succesfully built (the system now runs it) was
 r263345
 
 
 Hi,
 
 did see this (or something similar) too. Cured with 'make
 kernel-toolchain' and only then 'make buildkernel'. Could you try tis?

config recently added the -I option, so you need to rebuild your 
kernel-toolchain before things will work… Rebuilding -DNO_CLEAN will be fast 
enough.

Warner
___
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: (more) screen distortion with intel GPU / xorg on recent -HEAD?

2014-03-23 Thread Adrian Chadd
Less information-poor response:

* when it happens, the FB will resume correctly for a little bit, then
once everything comes back, it flips to being distorted. So, it's
likely something is misconfiguring stuff during resume.
* I can flip to VTs fine; I can login and do things fine;
* When I flip back to xorg, things still remain distorted;
* If I ctrl-C xorg and start it again, it starts back up correctly.

So hm, maybe the vt save/resume code learnt something buggy?


-a


On 23 March 2014 01:27, Adrian Chadd adr...@freebsd.org wrote:
 Hi,

 I know this is an information-poor message.

 The last time i updated my two test laptops was around the middle of
 last month. Back then, xorg would occasionally get distorted, but
 typically would come back from suspend fine.

 Lately, it seems a 50% chance that coming back from suspend that xorg
 will be not only distorted, but further screen redraws are wrong. It's
 like the framebuffer configuration is wrong and persists to be wrong.
 I have to exit out of xorg and restart it.

 Has anyone else seen this?


 -a
___
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: signal 8 (floating point exception) upon resume

2014-03-23 Thread Adrian Chadd
[snip]

Hi,

As part of this thread, a whole lot of stuff was thrown around to try
and fix / improve the correctness of this.

But it still happens to me in -HEAD i386. I updated to r263418 and
it's now doing it around 30-50% of the time I resume.

So, since I really am trying to avoid getting neck deep in learning
(by myself) a new thing right now, would someone be willing to help me
through the process of (a) learning how this is all supposed to work
(which thanks to jhb and bde, I think I've learnt from the posts in
this thread) and (b) some things to try out? I'll be able to report
the results of this pretty quickly.

I'd like to start work on supporting and power efficiency stuff on
some of the chromebook and tablet hardware using Intel stuff but it's
going to be totally moot if i386 suspend/resume (and vt/xorg, but
that's a different thread) is this busted. :-)

Thanks,


-a
___
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: (more) screen distortion with intel GPU / xorg on recent -HEAD?

2014-03-23 Thread Lars Engels
On Sun, Mar 23, 2014 at 01:36:29PM -0700, Adrian Chadd wrote:
 Less information-poor response:
 
 * when it happens, the FB will resume correctly for a little bit, then
 once everything comes back, it flips to being distorted. So, it's
 likely something is misconfiguring stuff during resume.
 * I can flip to VTs fine; I can login and do things fine;
 * When I flip back to xorg, things still remain distorted;
 * If I ctrl-C xorg and start it again, it starts back up correctly.

Setting a new wallpaper and / or restarting the distorted windows
un-distorts them.


pgpjV3j2WcNhv.pgp
Description: PGP signature


Re: FreeBSD 10 and zfsd

2014-03-23 Thread Mark Felder
Hi guys,

Any updates?
___
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: FreeBSD 10 and zfsd

2014-03-23 Thread Alan Somers
On Sun, Mar 23, 2014 at 4:23 PM, Mark Felder f...@freebsd.org wrote:
 Hi guys,

 Any updates?

I've been very busy, but I did finally get those two seqpacket related
bugs fixed in head.  The next step is finding time for the merge.
Right now my FreeBSD todo list goes:
1) Commit fixes for half a dozen FIB related bugs.  I already have
them fixed in my private stable/9 branch, but need to port the fixes
to HEAD.
2) Update the zfsd branch.

I think that I'll be able to get number 1 done next week, or at least
send patches out for review.  I don't know if I'll get to number 2.

-Alan
___
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: (more) screen distortion with intel GPU / xorg on recent -HEAD?

2014-03-23 Thread Adrian Chadd
No, this isn't a the buffer is messed up, this is a everything is
and stays messed up.

Starting new applications odes'nt fix it.

Minimising/maximising the applications again doesn't fix it.

This is a the framebuffer config seems busted, not the contents of
that 2d rectaugular area got messed up. Normally when there's
distortions triggering some kind of change in that area (ie: not a
redraw) is enough to fix it.


-a


On 23 March 2014 14:05, Lars Engels lars.eng...@0x20.net wrote:
 On Sun, Mar 23, 2014 at 01:36:29PM -0700, Adrian Chadd wrote:
 Less information-poor response:

 * when it happens, the FB will resume correctly for a little bit, then
 once everything comes back, it flips to being distorted. So, it's
 likely something is misconfiguring stuff during resume.
 * I can flip to VTs fine; I can login and do things fine;
 * When I flip back to xorg, things still remain distorted;
 * If I ctrl-C xorg and start it again, it starts back up correctly.

 Setting a new wallpaper and / or restarting the distorted windows
 un-distorts them.
___
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