Originally Posted by lee295012-gmail If you're seeing the desktop freezing under 3.16 and 3.17 with alloc_contig_range kernel errors it's being looked into. http://lists.freedesktop.org/archive...st/065842.html I'll keep monitoring that bug progress. Is there a list of all ACPI bugs in 3.17?
Originally Posted by WinEunuchs2Unix I'll keep monitoring that bug progress. Is there a list of all ACPI bugs in 3.17? not that i'm aware of, added cma=0 to grub suggested with the bug report and so far no problems.
Code: Alexey Kardashevskiy (1):PC, KVM, CMA: Fix regression caused by wrong get_order() use http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/CHANGES
Alexey Kardashevskiy (1):PC, KVM, CMA: Fix regression caused by wrong get_order() use
Greetings, Hopefully everyone knows by now that the 3.17RC2 kernel is released and at least on my system working fine (so far). There was a git pull on the 3.17RC2 so that the mentioned bugs and others could be fixed. Also, its release was delayed so as to coincide with Linux's 23 anniversity.
It, both RC1 abd RC2, craps out on creating Vbox modules which means it's still unusable for me. I need to have a virtual Win 7 running for certain progs, 3.16.1 thankfully works flawless ...
Originally Posted by Doug S That is odd. I can only assume something got clobbered. OK got my 3.15.10 back up and running. It was simple as advanced options boot, 'e' on the version, find "linux" command line, going to end, wiping out "acpi=off", F10 to continue boot. As far as 3.17-rc2 goes the keyboard is simply dead at the password screen. Even playing around with grub2 recovery mode where fstab is is read-only mode the down arrow key doesn't work to select options and the enter key to select the top option doesn't work. I've taken the suggestion "cma=0" and incorporated it into the 3.15.x kernels will no ill-effects. A little research shows cma "contiguous memory allocation" is something new and probably not used yet to assign huge chunks of memory to device drivers. Thanks to all the helpful advice to get back up and running again. Tonight I'll dig around to see how CONFIG_INPUT (or whatever the case may be) works. EDIT 1: "acpi=off" was just the first step in the kernel override. The next step was "noapic acpi=off" which brought up an erratic mouse pointer and slow as molasis keyboard that allowed me to enter a password before freezing. I noticed fewer red "fail" status on the boot splash screen (4 instead of 8)? Normal 3.15.10 kernel gives 4 red "fail". One is for bluetooth daemon which I don't use and tried to remove once and that took out network manager and my whole desktop / unity (long story). Next step is to find pause key for boot splash to read the red "fail" statuses and see if remedying them allows clean 3.17-rc2 boot. EDIT 2: Some suggest pressing the pause key during boot splash screen to read messages but that only clears the screen. In /var/log/kern.log sections are filled with copious amounts of "\00" in red. The line before is Appamor running a profile ironically named "sanitizer_helper". Reading the appamor man page is giving me a headache, I think I'll throw "White House Down" into the Blu-Ray player. Setting DEFAULT_GRUB="1>2" sets grub2's default boot to "Advanced Options, Kernel 3.15.10" so unattended the Laptop boots clean without 3.17-rc2. Using RSDT instead of XSDT in the ACPI tables during kernel configuration didn't help: Code: Aug 26 21:49:59 Satellite-L300 kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.15.10-031510-generic root=UUID=*secret?* ro cma=0 acpi=rsdt EDIT 3: I've opened every log I can find and other than being a little slower than 3.15.10 version 3.17-rc2 has far fewer error messages and nothing catastrophic. Indeed the \00's I saw earlier were most likely created when I hard powered off the machine. Fascinating. EDIT 4: I got it to boot once by unplugging the ASM1042 54mm ExpressCard PCI-e USB 3.0 host controller before booting and plugging it in afterwards. Was it that or the external SATA drive, or the USB Sound driver, or Kingston 64 GB travel mate or one of the two 4 port hubs? I'll never know since I couldn't replicate the successful boot. Weird things with the external mouse not working with built in USB 2.0 port properly but perfectly on the USB 3 card. I'm going to take a break from this for awhile and go back to complicated Kernel Driver for gm965temp to setup private/public keys for OpenSSL so I can install key rings so I can load the module without tainting the kernel. Interesting
Aug 26 21:49:59 Satellite-L300 kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.15.10-031510-generic root=UUID=*secret?* ro cma=0 acpi=rsdt
Last edited by WinEunuchs2Unix; August 29th, 2014 at 03:46 AM.
Just for testing purposes I installed it on a locked down install of Lucid (10.04) and it is amazing what it has done for it's performance. It has appeared to eliminate a bottleneck that existed and is working superbly fast and slick. Of course will try on Utopic.
Originally Posted by ventrical Just for testing purposes I installed it on a locked down install of Lucid (10.04) and it is amazing what it has done for it's performance. It has appeared to eliminate a bottleneck that existed and is working superbly fast and slick. Of course will try on Utopic. could you elaborate or point to a website that explains a "locked down install"? FTR I see 3.17-rc3 will have bug fixes for ACPI and file systems that FAIK might clean boot my hardware configuration.
3.17-rc3 amd64 here hangs on boot unless nomodeset is specified on linux boot line. Nomodeset limits resolution to 1024x768 and other nasties. Intel Core 2 Duo 3 gHz. Same with i386.
Last edited by jerrylamos; September 2nd, 2014 at 01:18 AM.
Somewhere I saw directions for removing the 3.17 kernel? Any clue? Thanks.
View Tag Cloud
Ubuntu Forums Code of Conduct