Closed haojiezhu closed 9 years ago
divx118
commented
9 years ago You are probably encountering https://github.com/dnschneid/crouton/issues/1278
Just try ls /sys/module/lsm/parameters/module_locking if you get an error file not found then you will be sure it is the issue.
haojiezhu
commented
9 years ago Thanks you for the fast reply. This does seem to be the cause of VirtualBox failure. I'll try to disable module_locking by kernel flag when I get home tonight.
Gemisheresy
commented
9 years ago i have that issue too, how exactly do i fix it. I am not sure what a kernel flag is or how to fix it
haojiezhu
commented
9 years ago Kernel flags can be used to enable/disable certain features in Linux kernel. Basically, you need to change some flags and repack the kernel to get VirtualBox to work again in Chrome OS 41.
You can run "enable-vmx.sh" script from DennisLfromGA in crosh shell to get this job done (https://gist.github.com/DennisLfromGA/cd3455530cec2a5a1ef4).
I suggest you visiting the following link to get a better understanding of kernel repacking - https://github.com/dnschneid/crouton/wiki/Repack-kernel-to-Enable-VT_x-for-Virtualbox
Gemisheresy
commented
9 years ago sigh this is gonna take me time to understand right now my task is to try and move it to a sd card but it will work after i update but then it system reboots
haojiezhu
commented
9 years ago If you just need to solve the reboot issue, you can use "sudo edit-chroot -r chrootname" to recover a backup.
If you don't have a backup, you can try to download an old version of crouton here: https://github.com/dnschneid/crouton/commits/releases/crouton Then run update: sudo sh ~/Downloads/crouton -u -n chrootname You might be able to enter chroot after this.
Gemisheresy
commented
9 years ago i have a backup but every time i try to up date it does the reboot problem and then i cant do the tasks i want to do unless i update. like trying to put it on to an sd card all it does is show me the options anytime i run the command then i update run the command it works but it does the reboot
Gemisheresy
commented
9 years ago i think my crouton was really out of date too
Gemisheresy
commented
9 years ago damn it now i messed up and cant find it
Gemisheresy
commented
9 years ago i renamed it -n by accident now i cant delete it please help
haojiezhu
commented
9 years ago try "sudo delete-chroot chrootname". If nothing else works, I think chrome os recovery with usb drive is the last thing to try. Of course, backup your files first.
DennisLfromGA
commented
9 years ago Also, 'sudo edit-chroot -ad' should prompt to delete all chroots - if you don't know their name(s) and want to get rid of them.
On Thu, Mar 5, 2015 at 3:25 PM, haojiezhu notifications@github.com wrote:
try "sudo delete-chroot chrootname". If nothing else works, I think chrome os recovery with usb drive is the last thing to try. Of course, backup your files first.
— Reply to this email directly or view it on GitHub https://github.com/dnschneid/crouton/issues/1474#issuecomment-77444294.
DennyL@GMail
fraserYT
commented
9 years ago Can someone please explain what it means to run the script from a crosh shell vs the regular shell that I boot into crouton through?
Gemisheresy
commented
9 years ago I found it with -a and deleted it
haojiezhu
commented
9 years ago To fraserYT: That's the crosh shell.
To DennisLfromGA: I tried your enable-vmx.sh script and successfully set the kernel flags. I can load vboxdrv after this. However, when I try to boot Windows XP in VirtualBox, my whole system reboots.
Here is something even weirder - If I update my chroot with the latest crouton and then try to enter chroot, my system reboots. After I get back into Chrome OS, I find out my system downgraded from 41.0.2272.76 to 40.0.2214.115. I am not kidding. And VirtualBox works perfectly fine and Windows XP boots as usual. If I click "Check for and apply updates" in "About Chrome OS", system upgrades to 41.0.2272.76 again and VirtualBox quit working. So I am sticking to Chrome OS 40.0.2214.115 right now. God knows when Google will auto-update my machine again. Can someone explain what's going on with the downgrade after reboot? I thought Chrome OS doesn't allow downgrade.
DennisLfromGA
commented
9 years ago @haojiezhu - Each time Chrome OS is upgraded, you'll have to re-run 'enable-vmx.sh', hopefully that's the only problem.
fraserYT
commented
9 years ago Thanks @haojiezhu, I thought that was the crosh shell, but when I type 'sudo sh ~/Downloads/enable-vmx.sh' I get the error 'This script has to be run from a Cros shell (as chronos or superuser) - exiting!'. Where am I going wrong?
haojiezhu
commented
9 years ago To fraserYT:
I also ran into that issue. I think it's because of file permission. Solved it by running "sudo chmod a+x enable-vmx.sh". You can also try "sudo chmod u+x enable-vmx.sh" and "sudo chmod g+x enable-vmx.sh".
If you still have problem, you can just open "enable-vmx.sh" with an editor and remove the following lines that check if you are running the script from a Crosh shell:
if [ "x$USER" != 'xchronos' -a "x$SUDO_USER" != 'xchronos' ]; then error 1 "This script has to be run from a Cros shell (as chronos or superuser) - exiting!" fi
haojiezhu
commented
9 years ago @DennisLfromGA, thanks a lot for the help and your script. I did re-run your script after system update. I verified kernel flags with "cat /proc/cmdline" and made sure vboxdrv is indeed loaded in Ubuntu with "sudo /etc/init.d/vboxdrv status". The problem is when I try to boot virtual machine (32-bit Windows XP in this case), whole system crashes and reboots.
After fiddling the thing for the whole morning, my tentative conclusion is that Google changed something in 41.0.2272.76 stable release and this probably caused all these troubles. Luckily, the weird system downgrade thing I mentioned kinda saved me temporarily. Right now I'm trying to block auto-update in my router.
picostove
commented
9 years ago It's too late now that you've downgraded, but if this problem appears again can you post the output of /dev/pstore/console-ramoops? That'll have the kernel logs and stack trace leading up to the panic that caused the reboot, which would help us establish if it's a cros kernel bug or something else.
Watney
commented
9 years ago A simple way to check if your system is configured to run virtual machines is to run kvm-ok which can be installed in the Ubuntu repo as part of cpu-checker
Source The Chromium Projects
Watney
commented
9 years ago @DennisLfromGA @divx118 Before I run enable-vmx.sh I'm trying to get my brain around all of the implications. I follow the script, and it executes the same commands in the Wiki to Enable VT_x. Basically, the script adds two lines to the kernel, disablevmx=off and lsm.module_locking=0.
What I'm confused about is disabling verified boot, dev_boot_signed_only=0.
Am I right in understanding that updating crouton re-enables the flag, dev_boot_signed_only=1? Is this what's causing users all sorts of problems?
To sum-up, before I add the lines to my kernel and disable verified boot, I'm trying to make sure I understand what to expect with each crouton -u and CrOS update. Thanks!!!
fraserYT
commented
9 years ago @haojiezhu Thanks. That allowed me to run the script, which didn't fix my problem, but I'll keep digging
divx118
commented
9 years ago @Watney Yes you are correct. You will need to set dev_boot_usb=1 dev_boot_legacy=1. If those also are set, crouton doesn't change the dev_boot_signed_only flag.
@DennisLfromGA ^^^
DennisLfromGA
commented
9 years ago @Watney -
Yep, what @divx118 said. ;)
There's a rather long and enlightening conversation about it here - https://github.com/dnschneid/crouton/issues/765#issuecomment-69986327
@fraserYT, @haojiezhu, et all,
I think I finally got the logic right in the 'enable-vmx.sh' script, it seems to work now. I was trying to make sure you were either 'chronos' or 'superuser' in Chrome OS.
dxia1
commented
9 years ago I "had" the same problem: after chromeOS updated to v.41 and I updated crouton, sudo startkde caused my chromebook to reboot. I found this thread and ran @DennisLfromGA 's script, but the reboot issue was still there. I updated my chroot again and the issue was still there.
Out of desperation I restored the chroot from my most recent backup. This time, sudo startkde worked. But what happened to @haojiezhu also happened to me; that is, chromeOS "downgraded" back to v.40.
This is very strange, and I'm afraid to update chromeOS for fear of the same issue recurring. Has anyone gotten to the bottom of this yet?
divx118
commented
9 years ago You "downgraded" because you ran @DennisLfromGA script, without setting dev_boot_usb=1 dev_boot_legacy=1 then when you upgrade your chroot dev_boot_signed_only=1 is set by crouton again. So on a reboot the not signed kernel with the adjusted kernel flags is skipped and the older kernel with rootfs is booted.
Chromeos has 2 kernel partitions (KERNEL A and B) and 2 rootfs partitions (ROOTFS A and B). When chromeos updates it will use the currently not booted kernel and rootfs and sets a bit to boot that the next time. So it keep switching with updates between A and B, hence you will have always the previous version on your chromebook which will boot when the other one failed.
Watney
commented
9 years ago 1) I followed @divx118 's advice, and set dev_boot_usb=1 dev_boot_legacy=1.
2) Then, I ran @DennisLfromGA 's script. Everything worked.
3) I rebooted and double checked with crossover and kvm-ok. Again, everything looked great.
4) So, I booted into -n vbox, launched VirtualBox and discovered the kernel isn't loading
5) So, back to troubleshooting, and discovered that sudo /etc/rc.local complains
chmod: cannot access '/sys/module/lsm/parameters/module_locking': No such file or directory
6) And, strangely, crossystem throws all sorts of errors
chronos@localhost / $ crossystem
arch = x86 # Platform architecture
backup_nvram_request = (error) # Backup the nvram somewhere at the next boot. Cleared on success.
block_devmode = (error) # Block all use of developer mode
clear_tpm_owner_request = (error) # Clear TPM owner on next boot
clear_tpm_owner_done = (error) # Clear TPM owner done
cros_debug = 1 # OS should allow debug features
dbg_reset = (error) # Debug reset mode request (writable)
ddr_type = unknown # Type of DDR RAM
debug_build = 0 # OS image built for debug features
dev_boot_usb = (error) # Enable developer mode boot from USB/SD(writable)
dev_boot_legacy = (error) # Enable developer mode boot Legacy OSes (writable)
dev_boot_signed_only = (error) # Enable developer mode boot only from official kernels (writable)
7) But, pressing Tab at boot shows that dev_boot_usb=1 dev_boot_legacy=1.
Any ideas what's borked? The only other thing that I tried along the way was to press Ctrl+L at the scary screen, even though my system doesn't support Legacy Boot (i.e., it doesn't ship with Coreboot).
[Edit] Checking chrome://system/ in the browser shows
1) the BIOS is correctly configured (dev_boot_usb=1, dev_boot_legacy=1, and dev_boot_signed_only = 0)
2) from demsg, the kernel command line includes disablevmx=off lsm.module_locking=0
3) KVM is successfully enabled.
Lastly,
Running within the chroot, sudo /etc/init.d/vboxdrv setup completes successfully, but alas, ls -al /sys/module/lsm/parameters returns ls: cannot access /sys/module/lsm/parameters: No such file or directory
tl;dr after modifying the BIOS and enabling kvm in the kernel, sudo /etc/rc.local complains
chmod: cannot access '/sys/module/lsm/parameters/module_locking': No such file or directory
DennisLfromGA
commented
9 years ago You need to use 'sudo' with the crossystem command - or be root. Sorry I can't help you with the vbox stuff, I haven't played with it (yet).
On Sun, Mar 8, 2015 at 8:08 PM, Watney notifications@github.com wrote:
1) I followed @divx118 https://github.com/divx118 's advice, and set dev_boot_usb=1 dev_boot_legacy=1. 2) Then, I ran @DennisLfromGA https://github.com/DennisLfromGA 's script. Everything worked. 3) I rebooted and double checked with crossover and kvm-ok. Again, everything looked great. 4) So, I booted into -n vbox, launched VirtualBox, but got a runtime error. 5) So, back to troubleshooting, and discovered that sudo /etc/rc.local it complains chmod: cannot access '/sys/module/lsm/parameters/module_locking': No such file or directory 6) And, strangely, crossystem throws all sorts of errors chronos@localhost / $ crossystem arch = x86 # Platform architecture backup_nvram_request = (error) # Backup the nvram somewhere at the next boot. Cleared on success. block_devmode = (error) # Block all use of developer mode clear_tpm_owner_request = (error) # Clear TPM owner on next boot clear_tpm_owner_done = (error) # Clear TPM owner done cros_debug = 1 # OS should allow debug features dbg_reset = (error) # Debug reset mode request (writable) ddr_type = unknown # Type of DDR RAM debug_build = 0 # OS image built for debug features dev_boot_usb = (error) # Enable developer mode boot from USB/SD(writable) dev_boot_legacy = (error) # Enable developer mode boot Legacy OSes (writable) dev_boot_signed_only = (error) # Enable developer mode boot only from official kernels (writable)
7) Pressing Tab at boot shows that dev_boot_usb=1 dev_boot_legacy=1.
Any ideas what's borked? The only other thing that I tried along the way was to press Ctrl+L at the scary screen, even though my system doesn't support Legacy Boot (i.e., it doesn't ship with Coreboot).
— Reply to this email directly or view it on GitHub https://github.com/dnschneid/crouton/issues/1474#issuecomment-77783664.
DennyL@GMail
tmagara
commented
9 years ago I got same reboot problem on ASUS ChromeBox since update to Chrome OS 41.
Here is my content of /dev/pstore/console-ramoops
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.8.11 (chrome-bot@build59-m2) (gcc version 4.9.x-google 20140827 (prerelease) (4.9.1_cos_gg_2f9796c_4.9.1-r82) ) #1 SMP Mon Mar 2 06:44:29 PST 2015
[ 0.000000] Command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2506752 verity payload=PARTUUID=1328478a-723d-794f-bc80-f00fd3956378/PARTNROFF=1 hashtree=PARTUUID=1328478a-723d-794f-bc80-f00fd3956378/PARTNROFF=1 hashstart=2506752 alg=sha1 root_hexdigest=741ce042d3b8474b67d4a226473443a361c9ad05 salt=a5244d04421135d9c9dcaa10bc5213664528aaf0c8743b167039eabaad46a108" noinitrd vt.global_cursor_default=0 kern_guid=1328478a-723d-794f-bc80-f00fd3956378 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000000fff] type 16
[ 0.000000] BIOS-e820: [mem 0x0000000000001000-0x000000000002ffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000000030000-0x000000000003ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000040000-0x000000000009ffff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000000efffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000000f00000-0x0000000000ffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000001000000-0x000000007f781fff] usable
[ 0.000000] BIOS-e820: [mem 0x000000007f782000-0x000000007f7fffff] type 16
[ 0.000000] BIOS-e820: [mem 0x000000007f800000-0x00000000821fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000f0000000-0x00000000f3ffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000017cdfffff] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] SMBIOS 2.7 present.
[ 0.000000] No AGP bridge found
[ 0.000000] e820: last_pfn = 0x17ce00 max_arch_pfn = 0x400000000
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] e820: last_pfn = 0x7f782 max_arch_pfn = 0x400000000
[ 0.000000] Using GB pages for direct mapping
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x7f781fff]
[ 0.000000] init_memory_mapping: [mem 0x100000000-0x17cdfffff]
[ 0.000000] ACPI: RSDP 00000000000f0000 00024 (v02 CORE )
[ 0.000000] ACPI: XSDT 000000007f78c0e0 00054 (v01 CORE COREBOOT 00000000 CORE 00000000)
[ 0.000000] ACPI: FACP 000000007f7902a0 000F4 (v03 CORE COREBOOT 00000000 CORE 00000001)
[ 0.000000] ACPI Error: Gpe0Block - 32-bit FADT register is too long (32 bytes, 256 bits) to convert to GAS struct - 255 bits max, truncating (20121018/tbfadt-201)
[ 0.000000] ACPI BIOS Bug: Warning: 32/64X length mismatch in FADT/Gpe0Block: 256/255 (20121018/tbfadt-567)
[ 0.000000] ACPI: DSDT 000000007f78c250 04042 (v02 COREv4 COREBOOT 20110725 INTL 20090123)
[ 0.000000] ACPI: FACS 000000007f78c210 00040
[ 0.000000] ACPI: HPET 000000007f7903a0 00038 (v01 CORE COREBOOT 00000000 CORE 00000000)
[ 0.000000] ACPI: APIC 000000007f7903e0 0005C (v01 CORE COREBOOT 00000000 CORE 00000000)
[ 0.000000] ACPI: MCFG 000000007f790440 0003C (v01 CORE COREBOOT 00000000 CORE 00000000)
[ 0.000000] ACPI: SSDT 000000007f791340 008A0 (v02 CORE COREBOOT 0000002A CORE 0000002A)
[ 0.000000] ACPI: SSDT 000000007f791be0 0005C (v02 CORE COREBOOT 0000002A CORE 0000002A)
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x00010000-0x00ffffff]
[ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
[ 0.000000] Normal [mem 0x100000000-0x17cdfffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00010000-0x0002ffff]
[ 0.000000] node 0: [mem 0x00040000-0x0009ffff]
[ 0.000000] node 0: [mem 0x00100000-0x00efffff]
[ 0.000000] node 0: [mem 0x01000000-0x7f781fff]
[ 0.000000] node 0: [mem 0x100000000-0x17cdfffff]
[ 0.000000] ACPI: PM-Timer IO Port: 0x1008
[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] enabled)
[ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-39
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[ 0.000000] smpboot: Allowing 2 CPUs, 0 hotplug CPUs
[ 0.000000] e820: [mem 0x82200000-0xefffffff] available for PCI devices
[ 0.000000] setup_percpu: NR_CPUS:4 nr_cpumask_bits:4 nr_cpu_ids:2 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 26 pages/cpu @ffff88017ca00000 s76096 r8192 d22208 u1048576
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1017066
[ 0.000000] Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2506752 verity payload=PARTUUID=1328478a-723d-794f-bc80-f00fd3956378/PARTNROFF=1 hashtree=PARTUUID=1328478a-723d-794f-bc80-f00fd3956378/PARTNROFF=1 hashstart=2506752 alg=sha1 root_hexdigest=741ce042d3b8474b67d4a226473443a361c9ad05 salt=a5244d04421135d9c9dcaa10bc5213664528aaf0c8743b167039eabaad46a108" noinitrd vt.global_cursor_default=0 kern_guid=1328478a-723d-794f-bc80-f00fd3956378 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic
[ 0.000000] device-mapper: init: will configure 1 devices
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
[ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 0.000000] __ex_table already sorted, skipping sort
[ 0.000000] xsave: enabled xstate_bv 0x3, cntxt size 0x240
[ 0.000000] Checking aperture...
[ 0.000000] No AGP bridge found
[ 0.000000] Memory: 3984128k/6240256k available (4856k kernel code, 2107384k absent, 148744k reserved, 4083k data, 704k init)
[ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] CONFIG_RCU_FANOUT set to non-default value of 32
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] NR_IRQS:4352 nr_irqs:512 16
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] Initial TSC value: 5813857320
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.001000] Initial usec timer 4164654
[ 0.001000] tsc: Detected 1396.850 MHz processor
[ 0.000003] Calibrating delay loop (skipped), value calculated using timer frequency.. 2793.70 BogoMIPS (lpj=1396850)
[ 0.000007] pid_max: default: 32768 minimum: 301
[ 0.000040] Security Framework initialized
[ 0.000043] Yama: becoming mindful.
[ 0.000058] Mount-cache hash table entries: 256
[ 0.000269] Initializing cgroup subsys freezer
[ 0.000296] CPU: Physical Processor ID: 0
[ 0.000297] CPU: Processor Core ID: 0
[ 0.001655] mce: CPU supports 7 MCE banks
[ 0.001673] CPU0: Thermal monitoring enabled (TM1)
[ 0.001685] process: using mwait in idle threads
[ 0.001690] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
[ 0.001690] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
[ 0.001690] tlb_flushall_shift: 6
[ 0.001868] Freeing SMP alternatives: 12k freed
[ 0.001873] ACPI: Core revision 20121018
[ 0.004801] acpi_enable!
[ 0.004817] ACPI mode enable smi_command = 0xb2 val = 0xe1
[ 0.004821] ftrace: allocating 21794 entries in 86 pages
[ 0.018335] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.028339] smpboot: CPU0: Intel(R) Celeron(R) 2955U @ 1.40GHz (fam: 06, model: 45, stepping: 01)
[ 0.028352] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
[ 0.028363] ... version: 3
[ 0.028365] ... bit width: 48
[ 0.028367] ... generic registers: 8
[ 0.028369] ... value mask: 0000ffffffffffff
[ 0.028371] ... max period: 0000ffffffffffff
[ 0.028372] ... fixed-purpose events: 3
[ 0.028374] ... event mask: 00000007000000ff
[ 0.029728] smpboot: Booting Node 0, Processors #1 OK
[ 0.044368] Brought up 2 CPUs
[ 0.044372] smpboot: Total of 2 processors activated (5587.40 BogoMIPS)
[ 0.044465] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[ 0.046226] devtmpfs: initialized
[ 0.048156] RTC time: 4:49:45, date: 03/09/15
[ 0.048211] NET: Registered protocol family 16
[ 0.049009] Switching to clocksource hpet
[ 0.049020] ACPI: bus type pci registered
[ 0.049076] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf0000000-0xf3ffffff] (base 0xf0000000)
[ 0.049079] PCI: MMCONFIG at [mem 0xf0000000-0xf3ffffff] reserved in E820
[ 0.053502] PCI: Using configuration type 1 for base access
[ 0.055215] bio: create slab <bio-0> at 0
[ 0.055309] ACPI: Added _OSI(Module Device)
[ 0.055312] ACPI: Added _OSI(Processor Device)
[ 0.055315] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.055317] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.059005] ACPI: Interpreter enabled
[ 0.059010] ACPI: (supports S0 S3 S5)
[ 0.059036] ACPI: Using IOAPIC for interrupt routing
[ 0.067446] ACPI: IRQ 14 override to level, high
[ 0.067654] ACPI: Power Resource [FNP0] (off)
[ 0.067696] ACPI: Power Resource [FNP1] (off)
[ 0.067734] ACPI: Power Resource [FNP2] (off)
[ 0.067773] ACPI: Power Resource [FNP3] (off)
[ 0.067810] ACPI: Power Resource [FNP4] (on)
[ 0.068435] ACPI: No dock devices found.
[ 0.068440] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.068522] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 0.068779] pci_root PNP0A08:00: ignoring host bridge window [mem 0x000cc000-0x000cffff] (conflicts with Video ROM [mem 0x000c0000-0x000cebff])
[ 0.068786] pci_root PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
[ 0.068822] PCI host bridge to bus 0000:00
[ 0.068825] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.068829] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
[ 0.068832] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
[ 0.068834] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
[ 0.068837] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000c3fff]
[ 0.068840] pci_bus 0000:00: root bus resource [mem 0x000c4000-0x000c7fff]
[ 0.068842] pci_bus 0000:00: root bus resource [mem 0x000c8000-0x000cbfff]
[ 0.068845] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff]
[ 0.068848] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
[ 0.068850] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
[ 0.068853] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff]
[ 0.068856] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff]
[ 0.068858] pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff]
[ 0.068861] pci_bus 0000:00: root bus resource [mem 0x000e8000-0x000ebfff]
[ 0.068864] pci_bus 0000:00: root bus resource [mem 0x000ec000-0x000effff]
[ 0.068866] pci_bus 0000:00: root bus resource [mem 0x000f0000-0x000fffff]
[ 0.068869] pci_bus 0000:00: root bus resource [mem 0x82200001-0xfebfffff]
[ 0.068872] pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed44fff]
[ 0.072047] pci 0000:00:1c.0: PCI bridge to [bus 01]
[ 0.074050] pci 0000:00:1c.1: PCI bridge to [bus 02]
[ 0.074106] pci 0000:00:1c.2: PCI bridge to [bus 03]
[ 0.074956] pci0000:00: Requesting ACPI _OSC control (0x1d)
[ 0.074984] pci0000:00: ACPI _OSC control (0x1d) granted
[ 0.075706] ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 12 14 15) *11, disabled.
[ 0.075757] ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 11 12 14 15) *10, disabled.
[ 0.075802] ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 12 14 15) *11, disabled.
[ 0.075847] ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 *11 12 14 15), disabled.
[ 0.075892] ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
[ 0.075937] ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 11 12 14 15) *0, disabled.
[ 0.075982] ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
[ 0.076033] ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 11 12 14 15) *0, disabled.
[ 0.076162] SCSI subsystem initialized
[ 0.076166] ACPI: bus type scsi registered
[ 0.076238] ACPI: bus type usb registered
[ 0.076261] usbcore: registered new interface driver usbfs
[ 0.076273] usbcore: registered new interface driver hub
[ 0.076307] usbcore: registered new device driver usb
[ 0.076419] chromeos_acpi: registering CHSW 0
[ 0.076582] chromeos_acpi: registering VBNV 0
[ 0.076585] chromeos_acpi: registering VBNV 1
[ 0.076879] chromeos_acpi: truncating buffer from 3072 to 1336
[ 0.077127] chromeos_acpi: installed
[ 0.077129] chromeos_acpi: chromeos_acpi: enabling S3 USB wake
[ 0.077154] Advanced Linux Sound Architecture Driver Initialized.
[ 0.077156] PCI: Using ACPI for IRQ routing
[ 0.079319] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[ 0.079328] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
[ 0.088427] pnp: PnP ACPI init
[ 0.088442] ACPI: bus type pnp registered
[ 0.088525] system 00:00: [mem 0xfed1c000-0xfed1ffff] has been reserved
[ 0.088528] system 00:00: [mem 0xfed10000-0xfed13fff] has been reserved
[ 0.088531] system 00:00: [mem 0xfed18000-0xfed18fff] has been reserved
[ 0.088534] system 00:00: [mem 0xfed19000-0xfed19fff] has been reserved
[ 0.088537] system 00:00: [mem 0xf0000000-0xf3ffffff] has been reserved
[ 0.088540] system 00:00: [mem 0xfed20000-0xfed3ffff] has been reserved
[ 0.088543] system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
[ 0.088547] system 00:00: [mem 0xfed45000-0xfed8ffff] could not be reserved
[ 0.088550] system 00:00: [mem 0x00f00000-0x00ffffff] has been reserved
[ 0.088907] system 00:03: [mem 0xfed00000-0xfed003ff] has been reserved
[ 0.089037] system 00:05: [io 0x1000-0x10fe] has been reserved
[ 0.089183] system 00:07: [io 0x0700-0x0707] has been reserved
[ 0.089187] system 00:07: [io 0x0710-0x0713] has been reserved
[ 0.089234] system 00:08: [io 0x0720] has been reserved
[ 0.089237] system 00:08: [io 0x0730-0x0737] has been reserved
[ 0.089822] pnp: PnP ACPI: found 14 devices
[ 0.089824] ACPI: ACPI bus type pnp unregistered
[ 0.096367] pci 0000:00:1c.1: BAR 9: assigned [mem 0x82300000-0x824fffff 64bit pref]
[ 0.096373] pci 0000:00:1c.2: BAR 8: assigned [mem 0x82500000-0x826fffff]
[ 0.096380] pci 0000:00:1c.2: BAR 9: assigned [mem 0x82700000-0x828fffff 64bit pref]
[ 0.096384] pci 0000:00:1c.1: BAR 7: assigned [io 0x4000-0x4fff]
[ 0.096389] pci 0000:00:1c.2: BAR 7: assigned [io 0x5000-0x5fff]
[ 0.096393] pci 0000:00:1c.0: PCI bridge to [bus 01]
[ 0.096397] pci 0000:00:1c.0: bridge window [io 0x2000-0x2fff]
[ 0.096403] pci 0000:00:1c.0: bridge window [mem 0xe0500000-0xe05fffff]
[ 0.096408] pci 0000:00:1c.0: bridge window [mem 0xe0400000-0xe04fffff 64bit pref]
[ 0.096415] pci 0000:00:1c.1: PCI bridge to [bus 02]
[ 0.096419] pci 0000:00:1c.1: bridge window [io 0x4000-0x4fff]
[ 0.096425] pci 0000:00:1c.1: bridge window [mem 0xe0600000-0xe06fffff]
[ 0.096430] pci 0000:00:1c.1: bridge window [mem 0x82300000-0x824fffff 64bit pref]
[ 0.096437] pci 0000:00:1c.2: PCI bridge to [bus 03]
[ 0.096440] pci 0000:00:1c.2: bridge window [io 0x5000-0x5fff]
[ 0.096446] pci 0000:00:1c.2: bridge window [mem 0x82500000-0x826fffff]
[ 0.096451] pci 0000:00:1c.2: bridge window [mem 0x82700000-0x828fffff 64bit pref]
[ 0.096474] pci 0000:00:1c.1: enabling device (0106 -> 0107)
[ 0.096484] pci 0000:00:1c.2: enabling device (0104 -> 0107)
[ 0.096599] NET: Registered protocol family 2
[ 0.096762] TCP established hash table entries: 32768 (order: 7, 524288 bytes)
[ 0.096859] TCP bind hash table entries: 32768 (order: 8, 1048576 bytes)
[ 0.097265] TCP: Hash tables configured (established 32768 bind 32768)
[ 0.097289] TCP: reno registered
[ 0.097295] UDP hash table entries: 2048 (order: 5, 196608 bytes)
[ 0.097372] UDP-Lite hash table entries: 2048 (order: 5, 196608 bytes)
[ 0.097501] NET: Registered protocol family 1
[ 0.097640] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 0.097644] software IO TLB [mem 0x7b780000-0x7f780000] (64MB) mapped at [ffff88007b780000-ffff88007f77ffff]
[ 0.098268] microcode: CPU0 sig=0x40651, pf=0x40, revision=0x15
[ 0.098275] microcode: CPU1 sig=0x40651, pf=0x40, revision=0x15
[ 0.098305] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[ 0.100637] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.100748] msgmni has been set to 7781
[ 0.101100] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.101104] io scheduler noop registered
[ 0.101106] io scheduler deadline registered
[ 0.101137] io scheduler cfq registered (default)
[ 0.101642] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
[ 0.101645] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[ 0.101660] pcieport 0000:00:1c.1: Signaling PME through PCIe PME interrupt
[ 0.101662] pci 0000:02:00.0: Signaling PME through PCIe PME interrupt
[ 0.101677] pcieport 0000:00:1c.2: Signaling PME through PCIe PME interrupt
[ 0.101698] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.101717] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 0.101835] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
[ 0.101840] ACPI: Power Button [PWRB]
[ 0.101890] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[ 0.101893] ACPI: Power Button [PWRF]
[ 0.101975] ACPI: Fan [FAN0] (off)
[ 0.102024] ACPI: Fan [FAN1] (off)
[ 0.102061] ACPI: Fan [FAN2] (off)
[ 0.102094] ACPI: Fan [FAN3] (off)
[ 0.102126] ACPI: Fan [FAN4] (on)
[ 0.102431] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 0.102481] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input2
[ 0.102518] ACPI: Requesting acpi_cpufreq
[ 0.107027] thermal LNXTHERM:00: registered as thermal_zone0
[ 0.107031] ACPI: Thermal Zone [THRM] (49 C)
[ 0.107308] Non-volatile memory driver v1.3
[ 0.107369] Linux agpgart interface v0.103
[ 0.107472] tpm_tis tpm_tis: registering reboot notifier [gentle shutdown]
[ 0.107498] tpm_tis tpm_tis: 1.2 TPM (device-id 0xB, rev-id 16)
[ 0.245109] [drm] Initialized drm 1.1.0 20060810
[ 0.245589] [drm] Memory usable by graphics device = 2048M
[ 0.269364] [drm:i915_write32] *ERROR* Unknown unclaimed register before writing to a090
[ 0.269504] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 0.269506] [drm] Driver supports precise vblank timestamp query.
[ 0.372900] fbcon: inteldrmfb (fb0) is primary device
[ 0.533909] Console: switching to colour frame buffer device 240x67
[ 0.543091] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 0.543094] i915 0000:00:02.0: registered panic notifier
[ 0.543110] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[ 0.543152] usbcore: registered new interface driver udl
[ 0.543865] loop: module loaded
[ 0.543871] lkdtm: No crash points registered, enable through debugfs
[ 0.543906] cros_ec_lpc cros_ec_lpc.0: EC ID not detected
[ 0.543911] cros_ec_lpc: probe of cros_ec_lpc.0 failed with error -25
[ 0.544079] ahci: SSS flag set, parallel bus scan disabled
[ 0.544098] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 2 ports 6 Gbps 0x1 impl SATA mode
[ 0.544103] ahci 0000:00:1f.2: flags: 64bit ncq ilck stag pm led clo only pio slum part deso sadm apst
[ 0.544341] scsi0 : ahci
[ 0.544438] scsi1 : ahci
[ 0.544485] ata1: SATA max UDMA/133 abar m2048@0xe0719000 port 0xe0719100 irq 60
[ 0.544488] ata2: DUMMY
[ 0.544628] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.544631] ehci-pci: EHCI PCI platform driver
[ 0.544643] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 0.544654] uhci_hcd: USB Universal Host Controller Interface driver
[ 0.544703] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 0.544753] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
[ 0.544935] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.544946] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.544949] usb usb1: Product: xHCI Host Controller
[ 0.544951] usb usb1: Manufacturer: Linux 3.8.11 xhci_hcd
[ 0.544954] usb usb1: SerialNumber: 0000:00:14.0
[ 0.545081] hub 1-0:1.0: USB hub found
[ 0.545091] hub 1-0:1.0: 8 ports detected
[ 0.545293] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 0.545331] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
[ 0.545354] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[ 0.545357] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.545360] usb usb2: Product: xHCI Host Controller
[ 0.545362] usb usb2: Manufacturer: Linux 3.8.11 xhci_hcd
[ 0.545364] usb usb2: SerialNumber: 0000:00:14.0
[ 0.545466] hub 2-0:1.0: USB hub found
[ 0.545474] hub 2-0:1.0: 4 ports detected
[ 0.548983] usbcore: registered new interface driver cdc_acm
[ 0.548985] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 0.548987] Initializing USB Mass Storage driver...
[ 0.549007] usbcore: registered new interface driver usb-storage
[ 0.549009] USB Mass Storage support registered.
[ 0.549020] usbcore: registered new interface driver ums-realtek
[ 0.549045] usbcore: registered new interface driver usbserial
[ 0.549055] usbcore: registered new interface driver usbserial_generic
[ 0.549063] usbserial: USB Serial support registered for generic
[ 0.549121] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[ 0.549527] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.549534] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 0.549820] rtc_cmos 00:06: RTC can wake from S4
[ 0.549970] rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
[ 0.550002] rtc0: alarms up to one month, 242 bytes nvram, hpet irqs
[ 0.550053] i801_smbus 0000:00:1f.3: SMBus using PCI Interrupt
[ 0.550294] device-mapper: ioctl: 4.23.1-ioctl (2012-12-18) initialised: dm-devel@redhat.com
[ 0.550360] device-mapper: verity-chromeos: dm-verity-chromeos registered
[ 0.550363] device-mapper: bootcache: version 0.1.0 loaded
[ 0.550437] cpuidle: using governor ladder
[ 0.550498] cpuidle: using governor menu
[ 0.550736] gsmi version 1.0 loaded
[ 0.550811] usbcore: registered new interface driver usbhid
[ 0.550813] usbhid: USB HID core driver
[ 0.558734] console [pstore-1] enabled
[ 0.558742] ramoops: attached 0x100000@0xf00000, ecc: 0
[ 0.558800] Netfilter messages via NETLINK v0.30.
[ 0.558822] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[ 0.558928] ctnetlink v0.93: registering with nfnetlink.
[ 0.559089] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 0.559119] TCP: cubic registered
[ 0.559125] Initializing XFRM netlink socket
[ 0.559273] NET: Registered protocol family 10
[ 0.559466] NET: Registered protocol family 17
[ 0.560495] Magic number: 7:864:817
[ 0.560815] ALSA device list:
[ 0.560823] No soundcards found.
[ 0.560844] Warning: unable to open an initial console.
[ 0.576509] atkbd serio0: GETID failed
[ 0.605178] atkbd serio0: atkbd: SETLEDS failed
[ 0.662514] atkbd serio0: GETID failed
[ 0.689136] atkbd serio0: atkbd: SETLEDS failed
[ 0.746464] atkbd serio0: GETID failed
[ 0.773085] atkbd serio0: atkbd: SETLEDS failed
[ 0.809041] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 0.809634] ata1.00: ATA-9: SanDisk SSD U110 16GB, U221000, max UDMA/133
[ 0.809659] ata1.00: 31277232 sectors, multi 1: LBA48 NCQ (depth 31/32)
[ 0.810935] ata1.00: configured for UDMA/133
[ 0.811298] scsi 0:0:0:0: Direct-Access ATA SanDisk SSD U110 U221 PQ: 0 ANSI: 5
[ 0.811658] sd 0:0:0:0: [sda] 31277232 512-byte logical blocks: (16.0 GB/14.9 GiB)
[ 0.811766] sd 0:0:0:0: [sda] Write Protect is off
[ 0.811810] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 0.815210] sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12
[ 0.816813] sd 0:0:0:0: [sda] Attached SCSI disk
[ 0.816845] device-mapper: init: attempting early device configuration.
[ 0.817197] device-mapper: init: adding target '0 2506752 verity payload=PARTUUID=1328478a-723d-794f-bc80-f00fd3956378/PARTNROFF=1 hashtree=PARTUUID=1328478a-723d-794f-bc80-f00fd3956378/PARTNROFF=1 hashstart=2506752 alg=sha1 root_hexdigest=741ce042d3b8474b67d4a226473443a361c9ad05 salt=a5244d04421135d9c9dcaa10bc5213664528aaf0c8743b167039eabaad46a108'
[ 0.817258] device-mapper: verity: Argument 0: 'payload=PARTUUID=1328478a-723d-794f-bc80-f00fd3956378/PARTNROFF=1'
[ 0.817282] device-mapper: verity: Argument 1: 'hashtree=PARTUUID=1328478a-723d-794f-bc80-f00fd3956378/PARTNROFF=1'
[ 0.817306] device-mapper: verity: Argument 2: 'hashstart=2506752'
[ 0.817323] device-mapper: verity: Argument 3: 'alg=sha1'
[ 0.817338] device-mapper: verity: Argument 4: 'root_hexdigest=741ce042d3b8474b67d4a226473443a361c9ad05'
[ 0.817359] device-mapper: verity: Argument 5: 'salt=a5244d04421135d9c9dcaa10bc5213664528aaf0c8743b167039eabaad46a108'
[ 0.820419] bio: create slab <bio-1> at 1
[ 0.820486] device-mapper: init: dm-0 is ready
[ 0.822835] EXT4-fs (dm-0): couldn't mount as ext3 due to feature incompatibilities
[ 0.823431] EXT4-fs (dm-0): mounting ext2 file system using the ext4 subsystem
[ 0.826411] EXT4-fs (dm-0): mounted filesystem without journal. Opts: (null)
[ 0.826455] VFS: Mounted root (ext2 filesystem) readonly on device 254:0.
[ 0.828372] atkbd serio0: GETID failed
[ 0.832824] devtmpfs: mounted
[ 0.836320] Freeing unused kernel memory: 704k freed
[ 0.836507] Write protecting the kernel read-only data: 8192k
[ 0.847036] Freeing unused kernel memory: 1276k freed
[ 0.848199] Freeing unused kernel memory: 148k freed
[ 0.854975] atkbd serio0: atkbd: SETLEDS failed
[ 0.897904] usb 1-4: new full-speed USB device number 2 using xhci_hcd
[ 0.910191] atkbd serio0: GETID failed
[ 0.910457] usb 1-4: string descriptor 0 malformed (err = -61), defaulting to 0x0409
[ 0.912514] usb 1-4: New USB device found, idVendor=13d3, idProduct=3393
[ 0.912530] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 0.936802] atkbd serio0: atkbd: SETLEDS failed
[ 0.936817] atkbd serio0: probe failed
[ 0.965465] atkbd serio1: GETID failed
[ 0.992119] atkbd serio1: atkbd: SETLEDS failed
[ 0.992139] atkbd serio1: probe failed
[ 1.018716] psmouse serio0: GETID probe failed, retrying...
[ 1.066869] usb 1-6: new high-speed USB device number 3 using xhci_hcd
[ 1.079085] usb 1-6: New USB device found, idVendor=05e3, idProduct=0608
[ 1.079100] usb 1-6: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 1.079112] usb 1-6: Product: USB2.0 Hub
[ 1.079576] hub 1-6:1.0: USB hub found
[ 1.079813] hub 1-6:1.0: 4 ports detected
[ 1.099870] tsc: Refined TSC clocksource calibration: 1396.766 MHz
[ 1.099888] Switching to clocksource tsc
[ 1.100613] psmouse serio1: GETID probe failed, retrying...
[ 1.158042] Chromium OS LSM: init_module locked module="/lib/modules/3.8.11/kernel/drivers/net/tun.ko" pid=75 cmdline="modprobe tun"
[ 1.158069] Chromium OS LSM: dev(254,0): read-only
[ 1.158079] Chromium OS LSM: module locking engaged.
[ 1.158926] tun: Universal TUN/TAP device driver, 1.6
[ 1.158939] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 1.162785] PPP generic driver version 2.4.2
[ 1.183324] systemd-udevd[81]: starting version 208
[ 1.206059] Unsafe core_pattern used with suid_dumpable=2. Pipe handler or fully qualified core dump path required.
[ 1.221519] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: commit=600
[ 1.224868] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: commit=600
[ 1.233848] usb 1-7: new high-speed USB device number 4 using xhci_hcd
[ 1.249733] usb 1-7: New USB device found, idVendor=05e3, idProduct=0727
[ 1.249749] usb 1-7: New USB device strings: Mfr=3, Product=4, SerialNumber=2
[ 1.249761] usb 1-7: Product: USB Storage
[ 1.249770] usb 1-7: Manufacturer: Generic
[ 1.249778] usb 1-7: SerialNumber: 000000000260
[ 1.260816] scsi2 : usb-storage 1-7:1.0
[ 1.360083] usb 1-6.3: new low-speed USB device number 5 using xhci_hcd
[ 1.376924] usb 1-6.3: New USB device found, idVendor=047d, idProduct=1020
[ 1.376939] usb 1-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1.376952] usb 1-6.3: Product: Kensington Expert Mouse
[ 1.376961] usb 1-6.3: Manufacturer: Kensington
[ 1.377076] usb 1-6.3: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 1.380326] input: Kensington Kensington Expert Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.3/1-6.3:1.0/input/input3
[ 1.380510] hid-generic 0003:047D:1020.0001: input,hidraw0: USB HID v1.10 Mouse [Kensington Kensington Expert Mouse] on usb-0000:00:14.0-6.3/input0
[ 1.416009] bio: create slab <bio-2> at 2
[ 1.421525] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: discard,commit=600
[ 1.443142] usb 1-6.4: new low-speed USB device number 6 using xhci_hcd
[ 1.484044] usb 1-6.4: New USB device found, idVendor=04d9, idProduct=2011
[ 1.484060] usb 1-6.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 1.484072] usb 1-6.4: Product: USB Keyboard
[ 1.484225] usb 1-6.4: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 1.484241] usb 1-6.4: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 1.496897] input: USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.4/1-6.4:1.0/input/input4
[ 1.497109] hid-generic 0003:04D9:2011.0002: input,hidraw1: USB HID v1.10 Keyboard [USB Keyboard] on usb-0000:00:14.0-6.4/input0
[ 1.504978] EXT4-fs (sda1): re-mounted. Opts: commit=600,data=ordered
[ 1.523663] input: USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.4/1-6.4:1.1/input/input5
[ 1.523896] hid-generic 0003:04D9:2011.0003: input,hidraw2: USB HID v1.10 Device [USB Keyboard] on usb-0000:00:14.0-6.4/input1
[ 1.715858] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[ 2.264917] scsi 2:0:0:0: Direct-Access Generic Power Saving USB 0260 PQ: 0 ANSI: 0
[ 2.425203] init: daisydog main process (1666) terminated with status 1
[ 2.425241] init: daisydog main process ended, respawning
[ 2.463922] init: daisydog main process (1692) terminated with status 1
[ 2.463956] init: daisydog main process ended, respawning
[ 2.465482] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 2.480068] init: daisydog main process (1716) terminated with status 1
[ 2.480104] init: daisydog main process ended, respawning
[ 2.498726] init: daisydog main process (1745) terminated with status 1
[ 2.498761] init: daisydog main process ended, respawning
[ 2.513751] init: daisydog main process (1765) terminated with status 1
[ 2.513788] init: daisydog main process ended, respawning
[ 2.533887] cfg80211: Calling CRDA to update world regulatory domain
[ 2.538497] init: daisydog main process (1799) terminated with status 1
[ 2.538536] init: daisydog main process ended, respawning
[ 2.552063] sd 2:0:0:0: [sdb] 123992064 512-byte logical blocks: (63.4 GB/59.1 GiB)
[ 2.552987] cfg80211: World regulatory domain updated:
[ 2.553000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 2.553012] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 2.553029] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 2.553040] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
[ 2.553052] sd 2:0:0:0: [sdb] Write Protect is off
[ 2.553062] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
[ 2.553074] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
[ 2.553090] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
[ 2.554380] sd 2:0:0:0: [sdb] No Caching mode page present
[ 2.554392] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 2.558098] sd 2:0:0:0: [sdb] No Caching mode page present
[ 2.558112] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 2.562645] init: daisydog main process (1837) terminated with status 1
[ 2.562684] init: daisydog main process ended, respawning
[ 2.572848] sdb: sdb1
[ 2.576882] sd 2:0:0:0: [sdb] No Caching mode page present
[ 2.576896] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 2.576908] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[ 2.596096] init: daisydog main process (1874) terminated with status 1
[ 2.596133] init: daisydog main process ended, respawning
[ 2.620299] init: daisydog main process (1901) terminated with status 1
[ 2.620443] init: daisydog main process ended, respawning
[ 2.645674] init: daisydog main process (1925) terminated with status 1
[ 2.645712] init: daisydog main process ended, respawning
[ 2.673578] init: daisydog main process (1938) terminated with status 1
[ 2.673633] init: daisydog respawning too fast, stopped
[ 3.245173] init: disable_echo main process (62) killed by TERM signal
[ 6.968899] low_mem: setting minfree to 211968 kB
[ 6.997517] fuse init (API version 7.20)
[ 7.049042] zsmalloc: module is from the staging directory, the quality is unknown, you have been warned.
[ 7.053064] zram: module is from the staging directory, the quality is unknown, you have been warned.
[ 7.053326] zram: num_devices not specified. Using default: 1
[ 7.053337] zram: Creating 1 devices ...
[ 7.077607] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 7.080578] r8169 0000:01:00.0 eth0: RTL8168g/8111g at 0xffffc90000034000, c4:54:44:4c:85:10, XID 0c000800 IRQ 63
[ 7.080595] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 7.165078] hda_codec: invalid CONNECT_LIST verb 5[1]:0
[ 7.165144] hda_codec: invalid CONNECT_LIST verb 6[1]:0
[ 7.165206] hda_codec: invalid CONNECT_LIST verb 7[1]:0
[ 7.165570] input: HDA Intel MID HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/sound/card0/input6
[ 7.165722] input: HDA Intel MID HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/sound/card0/input7
[ 7.165826] input: HDA Intel MID HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/sound/card0/input8
[ 7.198699] Bluetooth: Core ver 2.19
[ 7.198732] NET: Registered protocol family 31
[ 7.198740] Bluetooth: HCI device and connection manager initialized
[ 7.198757] Bluetooth: HCI socket layer initialized
[ 7.198767] Bluetooth: L2CAP socket layer initialized
[ 7.198787] Bluetooth: SCO socket layer initialized
[ 7.206105] usbcore: registered new interface driver btusb
[ 7.232251] Adding 5839256k swap on /dev/zram0. Priority:-1 extents:1 across:5839256k SS
[ 7.253762] usbcore: registered new interface driver ath3k
[ 7.254214] usb 1-4: USB disconnect, device number 2
[ 7.352266] r8169 0000:01:00.0 eth0: unable to load firmware patch rtl_nic/rtl8168g-1.fw (-2)
[ 7.356400] r8169 0000:01:00.0 eth0: link down
[ 7.356457] r8169 0000:01:00.0 eth0: link down
[ 7.356521] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 7.388420] ath: phy0: ASPM enabled: 0x43
[ 7.390045] ieee80211 phy0: Atheros AR9462 Rev:2 mem=0xffffc90016e80000, irq=19
[ 7.415193] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card1/input9
[ 7.415380] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card1/input10
[ 7.538810] usb 1-4: new full-speed USB device number 7 using xhci_hcd
[ 7.551233] usb 1-4: string descriptor 0 malformed (err = -61), defaulting to 0x0409
[ 7.553289] usb 1-4: New USB device found, idVendor=13d3, idProduct=3393
[ 7.553303] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 7.722592] r8169 0000:01:00.0 eth0: link down
[ 8.220780] cfg80211: Calling CRDA for country: US
[ 8.223913] cfg80211: Regulatory domain changed to country: US
[ 8.223926] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 8.223939] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm)
[ 8.223950] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 1700 mBm)
[ 8.223961] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2300 mBm)
[ 8.223972] cfg80211: (5490000 KHz - 5590000 KHz @ 80000 KHz), (N/A, 2300 mBm)
[ 8.223983] cfg80211: (5650000 KHz - 5730000 KHz @ 80000 KHz), (N/A, 2300 mBm)
[ 8.223994] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm)
[ 8.224005] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm)
[ 8.479635] i2c /dev entries driver
[ 8.956414] r8169 0000:01:00.0 eth0: link up
[ 8.956432] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 14.825089] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts:
[ 33.613020] r8169 0000:01:00.0 eth0: link down
[ 36.081859] r8169 0000:01:00.0 eth0: link up
[ 36.081888] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 63.002819] r8169 0000:01:00.0 eth0: link down
[ 65.455001] r8169 0000:01:00.0 eth0: link up
[ 65.455032] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 511.733526] EXT4-fs (sda1): re-mounted. Opts: commit=600,data=ordered
[ 638.435342] EXT4-fs (sda1): re-mounted. Opts: commit=600,data=ordered
[ 638.886810] systemd-logind[18746]: New seat seat0.
[ 638.896732] systemd-logind[18746]: New session c1 of user root.
[ 638.967257] systemd-logind[18746]: Removed session c1.
[ 638.979027] systemd-logind[18746]: New session c2 of user tmagara.
[ 639.062056] r8169 0000:01:00.0 eth0: link up
[ 639.062422] r8169 0000:01:00.0 eth0: link up
[ 639.604712] BUG: unable to handle kernel NULL pointer dereference at 0000000000000074
[ 639.604734] IP: [<ffffffff848c8206>] intel_crtc_page_flip+0x33/0x315
[ 639.604754] PGD 0
[ 639.604764] Oops: 0000 [#1] SMP
[ 639.606960] gsmi: Log Shutdown Reason 0x03
[ 639.606969] Modules linked in: i2c_dev uinput ath9k_btcoex ath9k_common_btcoex ath9k_hw_btcoex ath snd_hda_codec_realtek ath3k btusb bluetooth snd_hda_codec_hdmi memconsole mac80211 snd_hda_intel r8169 snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer zram(C) lzo_compress zsmalloc(C) fuse cfg80211 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ppp_async ppp_generic slhc tun
[ 639.607110] CPU 1
[ 639.607118] Pid: 18801, comm: Xorg Tainted: G C 3.8.11 #1
[ 639.607131] RIP: 0010:[<ffffffff848c8206>] [<ffffffff848c8206>] intel_crtc_page_flip+0x33/0x315
[ 639.607149] RSP: 0018:ffff8801744b7cb8 EFLAGS: 00010286
[ 639.607158] RAX: ffff88013cc7dc00 RBX: ffff8801756c4c00 RCX: 0000000000000201
[ 639.607169] RDX: ffff88014ebae840 RSI: ffff88015172f9c0 RDI: ffff8801781d1000
[ 639.607179] RBP: ffff8801744b7d00 R08: ffff88015172f9c0 R09: 0000000000000034
[ 639.607190] R10: 0000000000000000 R11: ffffffff84890ced R12: ffff8801781d0000
[ 639.607200] R13: ffff8801781d1000 R14: 0000000000000000 R15: ffff8801775c8000
[ 639.607212] FS: 00007f5ce1c3e9c0(0000) GS:ffff88017cb00000(0000) knlGS:0000000000000000
[ 639.607223] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 639.607233] CR2: 0000000000000074 CR3: 0000000153fd4000 CR4: 00000000000407e0
[ 639.607243] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 639.607254] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 639.607265] Process Xorg (pid: 18801, threadinfo ffff8801744b6000, task ffff880174747080)
[ 639.607276] Stack:
[ 639.607282] ffffffff8489d776 ffff88015172f9c0 0000000000000034 ffff88015172f9c0
[ 639.607305] ffff8801756c4c00 ffff88017804cc00 ffff8801781d1000 ffff8801756c4a00
[ 639.607326] ffff8801756c4400 ffff8801744b7d48 ffffffff8489dcef 0000000000000000
[ 639.607348] Call Trace:
[ 639.607359] [<ffffffff8489d776>] ? commit_crtc_state+0x3e/0x21c
[ 639.607371] [<ffffffff8489dcef>] commit_plane_state+0x215/0x280
[ 639.607383] [<ffffffff8489d482>] atomic_commit.isra.3+0x93/0xb4
[ 639.607394] [<ffffffff8489d4b4>] drm_atomic_commit+0x11/0x13
[ 639.607407] [<ffffffff848963e2>] drm_mode_page_flip_ioctl+0x1bd/0x230
[ 639.607419] [<ffffffff84886006>] drm_ioctl+0x2f5/0x3d2
[ 639.607430] [<ffffffff84896225>] ? drm_mode_gamma_get_ioctl+0xc7/0xc7
[ 639.607443] [<ffffffff8462f8b8>] ? mmput+0x1b/0xc9
[ 639.607457] [<ffffffff846b9b44>] ? get_pageblock_migratetype+0x10/0x12
[ 639.607469] [<ffffffff84702406>] ? mntput_no_expire+0x3f/0x13a
[ 639.607481] [<ffffffff846f7eeb>] do_vfs_ioctl+0x362/0x425
[ 639.607493] [<ffffffff8465af1b>] ? should_resched+0x9/0x25
[ 639.607505] [<ffffffff84ab8caf>] ? _cond_resched+0xe/0x1e
[ 639.607515] [<ffffffff846f801b>] sys_ioctl+0x6d/0xa5
[ 639.607527] [<ffffffff84aba502>] system_call_fastpath+0x16/0x1b
[ 639.607537] Code: e5 41 57 41 56 41 55 41 54 53 48 83 ec 20 48 8b 87 b8 00 00 00 4c 8b 27 4c 8b 70 50 48 8b 86 90 00 00 00 4d 8b bc 24 f0 03 00 00 <41> 8b 5e 74 39 5e 74 48 89 45 d0 b8 ea ff ff ff 0f 85 bd 02 00
[ 639.607748] RIP [<ffffffff848c8206>] intel_crtc_page_flip+0x33/0x315
[ 639.607762] RSP <ffff8801744b7cb8>
[ 639.607769] CR2: 0000000000000074
[ 639.607803] ---[ end trace 4c81c16679f99bf2 ]---
[ 639.616079] Kernel panic - not syncing: Fatal exception
[ 639.616126] Kernel Offset: 0x3600000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[ 639.616247] gsmi: Log Shutdown Reason 0x02
[ 639.625324] ACPI MEMORY or I/O RESET_REG.My workaround is to switch to xiwi target. It's working fine.
DennisLfromGA
commented
9 years ago I don't know what that kernel panic is all about... :( You're workaround/solution is excellent and one to remember - at least until this issue gets worked out.
On Mon, Mar 9, 2015 at 1:48 AM, Takafumi Magara notifications@github.com wrote:
I got same reboot problem on ASUS ChromeBox since update to Chrome OS 41.
Here is my content of /dev/pstore/console-ramoops
[ 0.000000] Initializing cgroup subsys cpu [mem 0x0000000000f00000-0x0000000000ffffff] reserved
...
[ 639.607803] ---[ end trace 4c81c16679f99bf2 ]--- [ 639.616079] Kernel panic - not syncing: Fatal exception [ 639.616126] Kernel Offset: 0x3600000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) [ 639.616247] gsmi: Log Shutdown Reason 0x02 [ 639.625324] ACPI MEMORY or I/O RESET_REG.
My workaround is to switch to xiwi target. It's working fine.
— Reply to this email directly or view it on GitHub https://github.com/dnschneid/crouton/issues/1474#issuecomment-77803479.
DennyL@GMail
divx118
commented
9 years ago @Watney Remove the lines related to /sys/module/lsm/parameters/module_locking from rc.local. You don't need them anymore when dev_boot_signed_only=0 is set.
haojiezhu
commented
9 years ago @divx118 Thanks for giving a clear explanation on the "downgrade" thing. Now I can experimenting upgrade again.
Since only users with certain models of Chromebook/Chromebox report rebooting issue, I wonder if all these are caused by Chrome OS switches to "Freon" graphics stack to replace X11 on selected models (http://www.phoronix.com/scan.php?page=news_item&px=Chrome-OS-Freon-Graphics). Just my wild guess.
Watney
commented
9 years ago @haojiezhu my experience is similar to yours.
sudo /etc/init.d/vboxdrv status. tl;dr Even after modifying the BIOS and kernel and confirming the VirtualBox LKMs are indeed loading, booting my Windows 7 VM instantly reboots my Chromebook.
divx118
commented
9 years ago @Watney can you try using NAT instead of bridged networking on virtualbox? See if that prevents the reboot. See https://github.com/dnschneid/crouton/issues/1420
haojiezhu
commented
9 years ago @divx118 I always use NAT for my virtual machine, it also reboots.
divx118
commented
9 years ago @haojiezhu But yours reboots upon entering the chroot and not when starting virtualbox, or did I misunderstood? If so, I don't think your issue has anything to do with virtualbox, but maybe like you said transition to freon.
haojiezhu
commented
9 years ago @divx118 I was actually talking about vbox reboot. If I use a backup chroot from a few days ago (crouton version 1-20150301132939~master:80da699e), I can enter chroot fine. After setting kernel flags, I can load vboxdrv, but vbox reboots when I boots Windows, which uses NAT.
I probably should make clear I was experiencing two types of reboot with Chrome OS 41.
Watney
commented
9 years ago @divx118 let me sum-up my findings. I'm on the dev channel (42.0.2311.10 glimmer_freon). I ...
-r trusty -n vbox -t xfce,keyboard,xorglsmod)divx118
commented
9 years ago @Watney @haojiezhu It could be that the kernel headers are a bit out of date. Those on the ppa are pretty old. I will see that I build and upload some new ones. Since this is related to the kernel headers and not crouton. I suggest we take this over to https://github.com/divx118/crouton-packages/issues/10 when you please post there your uname -r, so we can see which kernel versions are affected.
picostove
commented
9 years ago Closing this since @divx118 is tracking.
divx118
commented
9 years ago Just an update, issue is fixed for amd64 3.8.11 and 3.10.18 kernels. Other headers for the leftover kernels/arches will be updated soon. If there still are problems, then post on https://github.com/divx118/crouton-packages/issues/10 and I can reopen the bug.
Gemisheresy
commented
9 years ago So if I update my crouton it will be fine now?
Gemisheresy
commented
9 years ago I don't use a vitural box and every time I update crouton or my chroot it restarts my chrombook. I keep trying to do things like putting it on an SD card or flash drive but every time I try it just list all the options. Acer c720 and trusty
Watney
commented
9 years ago You might take a look at #1490
Hi,
I just updated my Asus Chromebox to Chrome OS 41.0.2272.76 from stable channel yesterday. After I updated my chroot (trusty with XFCE) to crouton version 1-20150304145447~master:550afdb3, my Chromebox simply reboots when I try to enter chroot with startxfce4 every time. So I rolled back my chroot to crouton version 1-20150301132939~master:80da699e with backup file, and I can enter chroot again. However, now VirtualBox stops working and complains about "vboxdrv not loaded". I tried to reinstall vboxdrv (sudo /etc/init.d/vboxdrv setup) and reinstall the script from divx118 (https://github.com/divx118/crouton-packages) with no success.
Any suggestion? Just wonder if anyone runs into similar issue. Thanks.