New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 922338 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 17
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Chromebox for meetings - the devices were rebooting and then need to be re-enrolled again.

Project Member Reported by ryutas@chromium.org, Jan 16

Issue description

ChromeOS version: 71.0.3578.94.
ChromeOS device model: Guado 
Case#: 17811752

Description: Chromebox for meetings - the devices were rebooting and then need to be re-enrolled again.

Steps to reproduce: There are no specific steps to reproduce the problem.

Current Behavior The several Chromeboxes for meeting are rebooting and then needing to be enrolled again.

Expected Behavior: the device should not reboot and needing to be enrolled again 

Notes:
Current CfM CrOS version is 68, hence we are requesting the customer to use current 68 CrOS.
Would be helpful if you can review the log files due to an enterprise customer case. 

Drive link to logs: 
H6MSCX001192
Device log:
https://drive.google.com/open?id=1XrJqe_z6GBQuYPISmtmdF36BJyyhD9it
Version:
https://drive.google.com/open?id=1FblVnkmaXMuVkF-KCnGG_MmCwRC0ZsoZ
Policy:
https://drive.google.com/open?id=1nQaUR0hMrzUQ5UFDP1iWoBc0AtyZPQS3

H6MSCX001350
Device log:
https://drive.google.com/open?id=135OrXUizYc-MsFQBftqvfz3XAV_N_19V
Version:
https://drive.google.com/open?id=1Q_p0hoRdjEZIIQSB_XR1YccTDt-4wDCE
Policy:
https://drive.google.com/open?id=1ki9xV1UrtFXc6TvCwvSOoUQhZQyY51bR


H6MSCX001350
Recent enrolled date: Jan 8, 2019
185 | 2019-01-07 16:25:01 | System boot | 156
186 | 2019-01-07 16:25:01 | SUS Power Fail
187 | 2019-01-07 16:25:01 | System Reset
188 | 2019-01-07 16:25:01 | ACPI Wake | S5
189 | 2019-01-07 16:25:01 | Wake Source | Power Button | 0
190 | 2019-01-07 16:25:17 | Kernel Event | Clean Shutdown
191 | 2019-01-07 16:25:18 | System boot | 157
192 | 2019-01-07 16:25:18 | System Reset
193 | 2019-01-07 16:25:18 | Wake Source | GPE # | 27
194 | 2019-01-08 07:03:36 | System boot | 158
195 | 2019-01-08 07:03:36 | SUS Power Fail
196 | 2019-01-08 07:03:36 | System Reset
197 | 2019-01-08 07:03:36 | ACPI Wake | S5
198 | 2019-01-08 07:03:36 | Wake Source | Power Button | 0
199 | 2019-01-09 07:03:39 | System boot | 159
200 | 2019-01-09 07:03:39 | SUS Power Fail
201 | 2019-01-09 07:03:39 | System Reset
202 | 2019-01-09 07:03:39 | ACPI Wake | S5
203 | 2019-01-09 07:03:39 | Wake Source | Power Button | 0

2019-01-07T21:25:20.406886+00:00 NOTICE kernel: [    0.000000] Linux version 3.14.0 (chrome-bot@swarm-cros-764) (gcc version 4.9.x 20150123 (prerelease) (4.9.2_cos_gg_4.9.2-r197-ac6128e0a17a52f011797f33ac3e7d6273a9368d_4.9.2-r197) ) #1 SMP PREEMPT Tue Dec 11 00:03:56 PST 2018
2019-01-07T21:25:20.406888+00:00 INFO kernel: [    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 3584000 verity payload=PARTUUID=fb7edb7f-3b77-6b4f-9d81-7eeb6193a6df/PARTNROFF=1 hashtree=PARTUUID=fb7edb7f-3b77-6b4f-9d81-7eeb6193a6df/PARTNROFF=1 hashstart=3584000 alg=sha1 root_hexdigest=90ecf2683f7dd03ae1c8b5a643cc20474ac3615c salt=c4e7f871bcffe826285a94f1dc64271f0a6be37de14882faee56ed37606bad1c" noinitrd vt.global_cursor_default=0 kern_guid=fb7edb7f-3b77-6b4f-9d81-7eeb6193a6df add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic  
2019-01-07T21:25:20.406892+00:00 INFO kernel: [    0.000000] e820: BIOS-provided physical RAM map:
2019-01-07T21:25:20.406893+00:00 INFO kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000000fff] type 16


H6MSCX001192
 Recent enrolled date: Jan 11, 2019
228 | 2019-01-10 10:17:29 | Kernel Event | Clean Shutdown
229 | 2019-01-10 10:17:29 | ACPI Enter | S5
230 | 2019-01-10 10:17:36 | System boot | 86
231 | 2019-01-10 10:17:36 | SUS Power Fail
232 | 2019-01-10 10:17:36 | System Reset
233 | 2019-01-10 10:17:36 | ACPI Wake | S5
234 | 2019-01-10 10:17:36 | Wake Source | Power Button | 0
235 | 2019-01-11 04:05:39 | System boot | 87
236 | 2019-01-11 04:05:39 | SUS Power Fail
237 | 2019-01-11 04:05:39 | System Reset
238 | 2019-01-11 04:05:39 | ACPI Wake | S5
239 | 2019-01-11 04:05:39 | Wake Source | Power Button | 0
240 | 2019-01-12 04:05:43 | System boot | 88
241 | 2019-01-12 04:05:43 | SUS Power Fail
242 | 2019-01-12 04:05:43 | System Reset
243 | 2019-01-12 04:05:43 | ACPI Wake | S5
244 | 2019-01-12 04:05:43 | Wake Source | Power Button | 0

2019-01-11T04:05:42.555468-05:00 INFO kernel: [    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 3584000 verity payload=PARTUUID=f771f175-a2e2-e947-92ac-e6b1a6e37dc6/PARTNROFF=1 hashtree=PARTUUID=f771f175-a2e2-e947-92ac-e6b1a6e37dc6/PARTNROFF=1 hashstart=3584000 alg=sha1 root_hexdigest=90ecf2683f7dd03ae1c8b5a643cc20474ac3615c salt=c4e7f871bcffe826285a94f1dc64271f0a6be37de14882faee56ed37606bad1c" noinitrd vt.global_cursor_default=0 kern_guid=f771f175-a2e2-e947-92ac-e6b1a6e37dc6 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic  
2019-01-11T04:05:42.555533-05:00 NOTICE kernel: [    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 (20131218/tbfadt-204)
2019-01-11T04:05:42.555705-05:00 NOTICE kernel: [    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 3584000 verity payload=PARTUUID=f771f175-a2e2-e947-92ac-e6b1a6e37dc6/PARTNROFF=1 hashtree=PARTUUID=f771f175-a2e2-e947-92ac-e6b1a6e37dc6/PARTNROFF=1 hashstart=3584000 alg=sha1 root_hexdigest=90ecf2683f7dd03ae1c8b5a643cc20474ac3615c salt=c4e7f871bcffe826285a94f1dc64271f0a6be37de14882faee56ed37606bad1c" noinitrd vt.global_cursor_default=0 kern_guid=f771f175-a2e2-e947-92ac-e6b1a6e37dc6 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic  
2019-01-11T04:05:42.556467-05:00 WARNING kernel: [    0.349944] cros_ec_lpc: probe of cros_ec_lpc.0 failed with error -25
2019-01-11T04:05:54.449213-05:00 ERR session_manager[755]: [ERROR:dbus_util.cc(13)] CreateError(...): Domain=dbus, Code=org.chromium.SessionManagerInterface.PubkeySetIllegal, Message=Could not verify that owner key belongs to this user.
2019-01-11T04:05:55.993761-05:00 NOTICE mount-encrypted[1646]: [0111/090542:ERROR:tpm1.cc(495)] encstateful space contents absent or too short.
2019-01-11T04:05:55.994592-05:00 NOTICE mount-encrypted[1646]: [0111/090542:ERROR:tpm1.cc(495)] encstateful space contents absent or too short. 

 

Comment 1 by marcore@chromium.org, Jan 17 (5 days ago)

I've checked both the debug logs
storage_info.txt:
ATA device, with non-removable media
	Model Number:       KINGSTON RBU-SNS4151S316GG2             
	Serial Number:      50026B7274039E2F    
	Firmware Revision:  S9FM02D5
	Transport:          Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0

, and it's this Known Issue:
https://support.google.com/meethardware/answer/6063095?hl=en
Chromebox for meetings resets when it loses power


If your Chromebox for meetings has a Kingston® solid-state drive (SSD), it might unenroll and reset to the initial setup screen when there is a loss of power.

Comment 2 by marcore@chromium.org, Jan 17 (5 days ago)

Status: WontFix (was: Untriaged)

Sign in to add a comment