Random reboots - Githubissues

drinkcat / chroagh

Chromium OS Archlinux Chroot Environment

BSD 3-Clause "New" or "Revised" License

241 stars 27 forks source link

Random reboots #44

Open Niksko opened 10 years ago

Niksko commented 10 years ago

I've been getting random shutdowns since installing chroagh a few days ago. It's happened four times since Monday, and it seems to happen without any warning and completely at random.

I'm running version 37.0.2062.53 beta (64-bit) on an Acer C720, an up to date Arch system, using Awesome WM.

croutonversion gives: crouton: version git release: arch architecture: x86_64 targets: keyboard,cli-extra host: version 5978.37.0 (Official Build) beta-channel peppy

Can anybody assist me in tracking down this bug. I'm happy to provide more info if somebody can tell me the commands to run.

drinkcat commented 10 years ago

I've been getting random shutdowns since installing chroagh a few days ago.

Shutdown or reboot? They usually indicate different problems (reboot can be a sign of kernel panic).

Did you ever experience this issue when just Chrome OS is running? How long have you had your Chromebook before you installed chroagh?

Are you running anything special when the Chromebook reboots? (game? anything intensive?)

Can you provide the output of sudo cat /dev/pstore/console-ramoops?

Niksko commented 10 years ago

Definitely shutdown
I can't remember experiencing this when just Chrome OS is running. It hay have happened once, but certainly not with this frequency. I've had the chromebook for ~6 months.
I think that every time it's happened has been while coding in pycharm, however this is not really something I'd call intensive. It was always while I was simply writing code, not actually executing it.
Does it have to be right after a shutdown occurs?

drinkcat commented 10 years ago

Do you want the output from inside the chroot, and does it have to be right after a shutdown occurs?

Inside or outside should not matter. Right after a shutdown, yes (I mean, no reboot in between at least).

Niksko commented 10 years ago

Ok, I'll get you the output next time it happens.

Not sure if this is relevant, but something interesting happens when I run that command. This is just during normal operation, not after a shutdown.

screenshot 2014-08-04 at 11 42 24 am

Text entry and console output is garbled. This persists if I exit the shell, but it's fine again if I close the crosh window and open a new one.

drinkcat commented 10 years ago

Text entry and console output is garbled. This persists if I exit the shell, but it's fine again if I close the crosh window and open a new one.

Yeah, that happens when a command prints some binary data (no idea why the log got corrupted though...). Typing reset should also fix that.