Re: suspend/resume regression
Head worked for me. Joseph Mingrone j...@ftfl.ca writes: On head, resume worked, but the fn-f4 keybinding didn't suspend. I had to use zzz. Joseph Mingrone j...@ftfl.ca writes: No problem with -head on the X220 as well. Joseph signature.asc Description: PGP signature
Re: suspend/resume regression
Kevin Oberman rkober...@gmail.com writes: I have narrowed it to between 283990 and 284074. Have to crash, so maybe someone else will track it down by tomorrow. I only see a handfull (10) commits in there that look like possible causes. 280434 is compiling right now as the prime candidate. Cool. I think you mean 284034 and not 280434. It certainly looks suspicious. I'm trying 284028, but it'll be awhile. It wouldn't boot with just the kernel, so I'll try building world as well. signature.asc Description: PGP signature
Re: suspend/resume regression
Adrian Chadd adrian.ch...@gmail.com writes: ok. I've updated my x230 to the latest -head and itis okay at suspend/resume. No problem with -head on the X220 as well. I can go acquire an x220 (now that they're cheap) to have as another reference laptop. You might ping Allan Jude. If I'm not mistaken he had at least two X220s at BSDCan. Maybe he'd be willing to part with one. signature.asc Description: PGP signature
Re: suspend/resume regression
Adrian Chadd adrian.ch...@gmail.com writes: does it always fail now? Yes. The behaviour I described is, so far with 15-20 tries, consistent. signature.asc Description: PGP signature
Re: suspend/resume regression
Kevin Oberman rkober...@gmail.com writes: On Sat, Jun 27, 2015 at 3:13 PM, Joseph Mingrone j...@ftfl.ca wrote: Adrian Chadd adrian.ch...@gmail.com writes: does it always fail now? Yes. The behaviour I described is, so far with 15-20 tries, consistent. I confirm that I see the similar behavior on my T520 ThinkPad, Sandy Bridge system. FreeBSD rogue 10.2-PRERELEASE FreeBSD 10.2-PRERELEASE #1 r284698: Mon Jun 22 09:25:11 PDT 2015 root@rogue:/usr/obj/usr/src/sys/GENERIC amd64 It has been working flawlessly since Adrian's ACPI update. As of now, it suspends fine, but it won't resume. I get a fan spin-up, but the power LED continues to pulse, indicating it is suspended and the logs show nothing after the suspend. Shall I start a binary hunt for the culprit? It will likely take a few kernel builds as my last known working kernel was in late May. -- Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 That sounds about right (when i915kms is loaded). Thanks for the update. I was trying r282199 from the end of April when a lot of stuff under /stable/10/sys/dev/drm2 got touched, but since you say it's working I'll move ahead to about two weeks ago. signature.asc Description: PGP signature
Re: suspend/resume regression
Adrian Chadd adrian.ch...@gmail.com writes: please start binary searching. I'll update my x230 tonight when I get home and see if -head is broken. On head, resume worked, but the fn-f4 keybinding didn't suspend. I had to use zzz. I'm trying different different revisions and I'll report back when I find something interesting. signature.asc Description: PGP signature
suspend/resume regression
This is on a Lenovo X220. Suspend/resume was working until some time between late April and last week's STABLE snapshot. Suspend always seems to work, but there are two issues with resume. 1) When i915kms isn't loaded, then resuming works, but the screen doesn't come back on. I'm able to ssh in to verify all is well. kern.vty=vt is set in /boot/loader.conf. I'm not positive that this wasn't a problem in the past since I always started the system up with xdm. 2) When i915kms is loaded, then resuming doesn't work and the system needs a hard restart. This definitely used to worked. For case 1), after the system has resumed and i915kms is then loaded the message below appears in /var/log/messages: Jun 26 17:42:22 phe kernel: error: [drm:pid0:intel_lvds_enable] *ERROR* timed out waiting for panel to power off If there is anything I can test or any useful information I left out, just let me know. Joseph signature.asc Description: PGP signature
Re: 9.1-RC3 fusefs-encfs problem ( ls: b: Bad file descriptor )
On Thu, Dec 6, 2012 at 3:00 AM, Özkan KIRIK ozkan.ki...@gmail.com wrote: I just installed fusefs-encfs from ports. There is something wrong while mounting the fuse. The output : root@host # kldstat Id Refs AddressSize Name 13 0x8020 13e0d58 kernel 21 0x81812000 a9bb fuse.ko root@host # encfs `pwd`/a `pwd`/b The directory /usr/home/sysadmin/a/ does not exist. Should it be created? (y,n) y The directory /usr/home/sysadmin/b does not exist. Should it be created? (y,n) y Creating new encrypted volume. Please choose from one of the following options: enter x for expert configuration mode, enter p for pre-configured paranoia mode, anything else, or an empty line will select standard mode. ? Standard configuration selected. Configuration finished. The filesystem to be created has the following properties: Filesystem cipher: ssl/aes, version 3:0:2 Filename encoding: nameio/block, version 3:0:1 Key Size: 192 bits Block Size: 1024 bytes Each file contains 8 byte header with unique IV data. Filenames encoded using IV chaining mode. File holes passed through to ciphertext. Now you will need to enter a password for your filesystem. You will need to remember this password, as there is absolutely no recovery mechanism. However, the password can be changed later using encfsctl. New Encfs Password: Verify Encfs Password: root@host # root@host # mount /dev/ada0p2 on / (ufs, local, journaled soft-updates) devfs on /dev (devfs, local, multilabel) /dev/fuse0 on /usr/home/b (fusefs, local, synchronous) root@host # cd b b: Not a directory. root@host # ls b ls: b: Bad file descriptor root@host # umount b umount: b: stat: Bad file descriptor umount: b: unknown file system root@host # umount /usr/home/b - has no errors. I tried this on two different machines with 9.1-RC3 amd64. How can we solve this problem? Sincerely, Ozkan KIRIK I have the same problem. Downgrading sysutils/fusefs-kmod and sysutils/fusefs-libs as described in the PR linked to below allowed me to mount again. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/173240 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
