kitakar5525 / chromeos-kernel-linux-surface Goto Github PK

View Code? Open in Web Editor NEW

18.0 18.0 1.0 3.36 MB

linux-surface kernel for chromiumos.

License: GNU General Public License v3.0

Shell 100.00%

chromeos linux-kernel

chromeos-kernel-linux-surface's People

Contributors

Stargazers

Watchers

Forkers

liucaidong

chromeos-kernel-linux-surface's Issues

Auto mode change into tablet_mode not working

While auto mode change is not working, you can manually change the mode by keyboard.

To do so, add a flag --ash-debug-shortcuts to your /etc/chrome_dev.conf,
then restart your ui sudo restart ui, after that, you can change the mode by Ctrl+Alt+Shift+T.

# mount root filesystem as writable
sudo mount / -o rw,remount

# Edit this file
sudo vim /etc/chrome_dev.conf

Chrome OS Flex?

Would these kernel modifications work on Chrome OS Flex or is the kernel locked? Trying to get keyboard and touchscreen working on Surface Laptop 1. Thanks.

LoadPin module can't handle compressed modules

I can compress the modules:

CONFIG_MODULE_COMPRESS=y
CONFIG_MODULE_COMPRESS_GZIP=y

but Chromium OS will not load the compressed modules (fail to boot).

Auto-rotation not working

While auto rotation is not working, you can rotate your screen by:

If you are in tablet_mode:
- Use this android app: azw413/ChromeOSRotate: Android App to rotate orientation on Chrome Tablets

If you are not in tablet_mode:
- Ctrl+Shift+Reload (Ctrl+Shift+Super(Win)+F3)

Touch input not working after IPTS reset (0x80000005 failed status = 11)

Sometimes IPTS will reset itself on Chromium OS:

kern  :err   : [ 1494.058680] ipts mei::3e8d0870-271a-4208-8eb5-9acb9402ae04:0F: 0x80000005 failed status = 11
kern  :info  : [ 1494.058688] DEBUG: ipts_stop called
kern  :info  : [ 1494.058692] DEBUG: ipts_send_sensor_quiesce_io_cmd called
kern  :info  : [ 1494.059630] DEBUG: ipts_send_sensor_clear_mem_window_cmd called
kern  :info  : [ 1494.061624] DEBUG: ipts_send_sensor_quiesce_io_cmd called
kern  :info  : [ 1494.061832] DEBUG: ipts_start called
kern  :info  : [ 1494.096182] input: ipts 1B96:005E Pen as /devices/pci0000:00/0000:00:16.4/mei::3e8d0870-271a-4208-8eb5-9acb9402ae04:0F/0044:1B96:005E.0004/input/input50
kern  :info  : [ 1494.096869] input: ipts 1B96:005E as /devices/pci0000:00/0000:00:16.4/mei::3e8d0870-271a-4208-8eb5-9acb9402ae04:0F/0044:1B96:005E.0004/input/input51
kern  :info  : [ 1494.097078] input: ipts 1B96:005E UNKNOWN as /devices/pci0000:00/0000:00:16.4/mei::3e8d0870-271a-4208-8eb5-9acb9402ae04:0F/0044:1B96:005E.0004/input/input55
kern  :info  : [ 1494.097767] hid-multitouch 0044:1B96:005E.0004: input,hidraw2: <UNKNOWN> HID v16900.00 Mouse [ipts 1B96:005E] on heci3
kern  :info  : [ 1494.097842] DEBUG: ipts_send_sensor_clear_mem_window_cmd called
kern  :err   : [ 1494.099123] ipts mei::3e8d0870-271a-4208-8eb5-9acb9402ae04:0F: touch enabled 4
kern  :err   : [ 1494.103526] ipts mei::3e8d0870-271a-4208-8eb5-9acb9402ae04:0F: 0x80000005 failed status = 4
kern  :err   : [ 1494.107274] ipts mei::3e8d0870-271a-4208-8eb5-9acb9402ae04:0F: touch enabled 4

However, after the reset, Chromium OS will not recognize the touch input anymore.
But IPTS may still be working. You can confirm that by evtest.

So, the issues are:

how to get Chromium OS to recognize the IPTS touch input device again after the reset?
why does the reset (0x80000005 failed status = 11) happen? I've never seen this reset on Arch Linux

How to prepare kernel headers for building kernel modules?

I want to provide a kernel header package like linux-headers package on Arch Linux to build kernel modules.

Taking a screenshot using Pow+VolDown not working

Not working at least on SB1 and Surface 3.

i2c_hid: sensor device: output "failed to retrieve report from device" repeatedly after suspend

After suspend, error messages will be printed repeatedly.

On Surface 3:

kern  :err   : [  552.529630] i2c_hid i2c-MSHW0102:00: failed to retrieve report from device.

On Surface Book 1:

kern  :err   : [ 3077.026112] i2c_hid i2c-MSHW0030:00: failed to retrieve report from device.

Seems to be no impact on functionality, though. I can still read sensor values.

# on Surface Book 1
$ grep -H . /sys/bus/iio/devices/iio\:device?/in*_raw
/sys/bus/iio/devices/iio:device0/in_illuminance_raw:314
/sys/bus/iio/devices/iio:device0/in_intensity_both_raw:314
/sys/bus/iio/devices/iio:device1/in_rot_quaternion_raw:0 0 0 0 
/sys/bus/iio/devices/iio:device2/in_accel_x_raw:50
/sys/bus/iio/devices/iio:device2/in_accel_y_raw:-955
/sys/bus/iio/devices/iio:device2/in_accel_z_raw:-274
/sys/bus/iio/devices/iio:device3/in_anglvel_x_raw:93
/sys/bus/iio/devices/iio:device3/in_anglvel_y_raw:-49
/sys/bus/iio/devices/iio:device3/in_anglvel_z_raw:-16

But still those messages are annoying. Reloading i2c_hid module (if you build it as module) after suspend will suppress the messages.

There is no such issue on Arch Linux kernel.

chromeos-4.19: can't enable DMA for surface3-spi

surface3-spi uses PIO on both general and minimal config on chromeos-4.19 by default. Why?

$ echo "file drivers/spi/spi-pxa2xx.c +p" | sudo tee /sys/kernel/debug/dynamic_debug/control
$ dmesg -xw # then make a touch input
kern  :debug : [  446.556454] Surface3-spi spi-MSHW0037:00: 7692307 Hz actual, PIO

It uses DMA by default on chromeos-5.4 with both general and minimal config.

sysfs sensor values not updated on Surface 3

It seems to be sensors are not working on Surface 3.

Sensor values are not updated on Surface 3:

# On Surface 3
$ grep -H . /sys/bus/iio/devices/iio:device?/in*_raw
/sys/bus/iio/devices/iio:device0/in_illuminance_raw:0
/sys/bus/iio/devices/iio:device0/in_intensity_both_raw:0
/sys/bus/iio/devices/iio:device1/in_anglvel_x_raw:0
/sys/bus/iio/devices/iio:device1/in_anglvel_y_raw:0
/sys/bus/iio/devices/iio:device1/in_anglvel_z_raw:0
/sys/bus/iio/devices/iio:device2/in_accel_x_raw:0
/sys/bus/iio/devices/iio:device2/in_accel_y_raw:0
/sys/bus/iio/devices/iio:device2/in_accel_z_raw:-1000
/sys/bus/iio/devices/iio:device3/in_rot_quaternion_raw:0 0 0 0

On the other hand, it's working on Surface Book 1:

# On SB1
grep -H . /sys/bus/iio/devices/iio:device?/in*_raw
/sys/bus/iio/devices/iio:device0/in_anglvel_x_raw:0
/sys/bus/iio/devices/iio:device0/in_anglvel_y_raw:0
/sys/bus/iio/devices/iio:device0/in_anglvel_z_raw:0
/sys/bus/iio/devices/iio:device1/in_illuminance_raw:321
/sys/bus/iio/devices/iio:device1/in_intensity_both_raw:321
/sys/bus/iio/devices/iio:device2/in_accel_x_raw:49
/sys/bus/iio/devices/iio:device2/in_accel_y_raw:-970
/sys/bus/iio/devices/iio:device2/in_accel_z_raw:-263
/sys/bus/iio/devices/iio:device3/in_rot_quaternion_raw:0 0 0 0

chromeos-5.4: backlight not adjustable

Somehow backlight not adjustable on Surface 3 with both general and minimal config of chromeos-5.4.

Affected:

5.4.50-general-surface-k5-06734-g912c6036578d
5.4.50-minimal-surface-k5-06734-g912c6036578d

Works on Arch Linux with 5.4.50-1-lts with its kernel config.

I recommend using chromeos-4.19 kernels for now...

Sensors not working; caused by "FROMLIST: Input: atkbd: Receive and use physcode->keycode mapping from FW" (?)

At least on Surface 3, I found sensors seem to be not working (no auto-rotation with this patch) on the latest chromeos-4.19 4.19.114.

This issue won't happen on the latest linux-surface 4.19 kernel (4.19.114-1-surface-lts) with Arch Linux.
Also not happen on chromeos-5.4 5.4.30.

I tried chromeos-4.19 4.19.113 (commit 5080748) and it's working. After chromeos-4.19 4.19.114 (commit 0f61ed8), it's not working anymore.

I haven't yet found what is causing this issue.

wifi/bt unstable when using with iwl7000

First thanks a lot for your work and effort. I managed to get my Surface Pro 7 going with your kernel.
Wifi and Bluetooth are not working correctly, I tried different firmware for this card. Wifi is slow and doping out. I have the same laptop running with Arch Linux (Kernel 5.6.11) no problems.

Is there a specific surface 3 fix what you applied, so if I build the kernel a can maybe remove them?

Direct firmware load for firmware file failed with error -2

When you build driver as built-in, if the driver uses firmware file, you may see the following message on dmesg:

Direct firmware load for *firmware file* failed with error -2

BYT/CHT: backlight not adjustable when i915 is built-in (driver initialization order, pwm vs i915)

To adjust the backlight on Surface 3, we need to build i915 as not built-in but module.
Maybe the cause of this problem is that i915 will be loaded too early when built as built-in.

For now, I have to build DRM_I915 and modules which depend on it as module.

- DRM_I915
  - CONFIG_HDMI_LPE_AUDIO
  - INTEL_IPTS

GPIO-related issues (touchscreen input & some tablet buttons not working) after chromeos-4.19 4.19.104

On Surface 3, I found there is a GPIO-related issues, like touchscreen input & some tablet buttons (Vol-Up and Windows button that is located on right side of display) not working on the latest chromeos-4.19 4.19.114.
There may be another issue(s) that I didn't noticed.

This issue won't happen on the latest linux-surface 4.19 kernel (4.19.114-1-surface-lts) with Arch Linux.
Also not happen on chromeos-5.4 5.4.30.

I tried chromeos-4.19 4.19.103 and it's working. After chromeos-4.19 4.19.104, it's not working anymore.

So, maybe this commit (https://chromium.googlesource.com/chromiumos/third_party/kernel/+/383d9bec92939d1d34c1097358590d75ddc87c2b) caused this issue?

I've built a kernel with that commit reverted. I'll check now.

GENTOO: Kernel config will be overridden automatically before building

When building using cros_workon_make, kernel config may be overridden by someone:

$ FEATURES="noclean" cros_workon_make --board=${BOARD} chromeos-kernel-4_19 --install
[...]
13:38:51 >>> Configuring source in /mnt/host/source/src/third_party/kernel/v4.19 ...
 * Using kernel config: chromiumos-x86_64
 *    - enabling Enable ACPI AC config
 *    - disabling framebuffer console config
 *    - enabling Support running virtual machines with KVM config
 *    - enabling CDC MBIM driver config
 *    - enabling TPM support config
 *    - enabling Transparent Hugepage Support config
 *    - enabling Virtual USB support config
 *    - enabling Virtual Video Test Driver config
 *    - enabling 802.1Q VLAN config
 *    - disabling VT console config
make -j48 O=/build/amd64-generic/var/cache/portage/sys-kernel/chromeos-kernel-4_19 LD=/usr/x86_64-pc-linux-gnu/x86_64-cros-linux-gnu/binutils-bin/2.27.0/ld 'CC=x86_64-cros-linux-gnu-clang -B/usr/x86_64-pc-linux-gnu/x86_64-cros-linux-gnu/binutils-bin/2.27.0' 'CXX=x86_64-cros-linux-gnu-clang++ -B/usr/x86_64-pc-linux-gnu/x86_64-cros-linux-gnu/binutils-bin/2.27.0' HOSTCC=x86_64-pc-linux-gnu-clang HOSTCXX=x86_64-pc-linux-gnu-clang++ olddefconfig 
make[1]: Entering directory '/build/amd64-generic/var/cache/portage/sys-kernel/chromeos-kernel-4_19'
  GEN     ./Makefile
scripts/kconfig/conf  --olddefconfig Kconfig
.config:794:warning: override: reassigning to symbol FRAMEBUFFER_CONSOLE
.config:803:warning: override: reassigning to symbol KVM
.config:808:warning: override: reassigning to symbol KVM_INTEL
.config:810:warning: override: reassigning to symbol VSOCKETS
.config:811:warning: override: reassigning to symbol VHOST_VSOCK
.config:819:warning: override: reassigning to symbol TCG_TPM
.config:820:warning: override: reassigning to symbol TCG_TIS
#
# configuration written to .config
#
make[1]: Leaving directory '/build/amd64-generic/var/cache/portage/sys-kernel/chromeos-kernel-4_19'
13:38:54 >>> Source configured.
[...]

config-minimal-surface: no text output on initramfs (when using with brunch)

Some kernel configs are missing.

chromeos-5.4: tpm_tis causes kernel oops

Not bootable on SB1 !!!. It reboots on chrome logo. (But works well on Surface 3... why?)
~~I released this binary anyway because it works with Surface 3. I'll look into what's happening on SB1 later.~~
~~So, if you want to use v5.4 kernels but this release doesn't work, try 5.4.24 version for now.~~
EDIT: after installing other kernel version then reinstalling this version, it started working on SB1. Hmm?

https://github.com/kitakar5525/chromeos-kernel-linux-surface/releases/tag/chromeos-v5.4.39.r4076.d37238f2773c3-surface-brunch

I sometimes encounter that v5.4 kernels don't boot on SB1; it turned out that tpm_tis module causes kernel oops:

dmesg log

#
# sudo modprobe tpm_tis
#
kern  :debug : [  347.275763] acpi IFX0562:00: GPIO: looking up 0 in _CRS
kern  :info  : [  347.281797] tpm_tis IFX0562:00: 2.0 TPM (device-id 0x1A, rev-id 16)
kern  :alert : [  347.302914] BUG: unable to handle page fault for address: ffffb14b40372000
kern  :alert : [  347.302930] #PF: supervisor read access in kernel mode
kern  :alert : [  347.302937] #PF: error_code(0x0000) - not-present page
kern  :info  : [  347.302944] PGD 45d561067 P4D 45d561067 PUD 45d564067 PMD 45cdcc067 PTE 0
kern  :warn  : [  347.302959] Oops: 0000 [#1] PREEMPT SMP PTI
kern  :warn  : [  347.302970] CPU: 1 PID: 8555 Comm: modprobe Tainted: G         C        5.4.43-04966-g44ecd9e48613 #21
kern  :warn  : [  347.302980] Hardware name: Microsoft Corporation Surface Book/Surface Book, BIOS 92.3192.768 03.24.2020
kern  :warn  : [  347.302998] RIP: 0010:tpm_read_log_efi+0x17c/0x1b8 [tpm]
kern  :warn  : [  347.303008] Code: e8 d8 50 a4 c3 eb 41 48 89 83 68 07 00 00 41 8b 55 04 4c 01 f0 41 bc 02 00 00 00 48 89 c7 48 63 0d 02 db 31 c5 48 8d 74 15 10 <f3> a4 48 63 05 f4 da 31 c5 49 01 c6 4c 03 b3 68 07 00 00 4c 89 b3
kern  :warn  : [  347.303025] RSP: 0018:ffffb14b6a813b00 EFLAGS: 00010286
kern  :warn  : [  347.303033] RAX: ffff9c79aa0ec7a9 RBX: ffff9c789fd99000 RCX: fffffffffffff0a1
kern  :warn  : [  347.303042] RDX: 0000000000000a19 RSI: ffffb14b40372000 RDI: ffff9c79aa0ecd80
kern  :warn  : [  347.303050] RBP: ffffb14b40371000 R08: 0000000000000000 R09: 8000000000000063
kern  :warn  : [  347.303059] R10: 000ffffffffff000 R11: 0000000000000001 R12: 0000000000000002
kern  :warn  : [  347.303067] R13: ffff9c7904d98018 R14: 00000000000047a9 R15: ffff9c7c311f2328
kern  :warn  : [  347.303076] FS:  00007ead3aa90740(0000) GS:ffff9c7cdf280000(0000) knlGS:0000000000000000
kern  :warn  : [  347.303086] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kern  :warn  : [  347.303093] CR2: ffffb14b40372000 CR3: 0000000102a04004 CR4: 00000000003606e0
kern  :warn  : [  347.303101] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
kern  :warn  : [  347.303110] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
kern  :warn  : [  347.303117] Call Trace:
kern  :warn  : [  347.303133]  tpm_bios_log_setup+0x67/0x16e [tpm]
kern  :warn  : [  347.303146]  tpm_chip_register+0x8d/0x248 [tpm]
kern  :warn  : [  347.303159]  tpm_tis_core_init+0x5b5/0x601 [tpm_tis_core]
kern  :warn  : [  347.303176]  tpm_tis_plat_probe+0xa0/0xbe [tpm_tis]
kern  :warn  : [  347.303191]  platform_drv_probe+0x44/0x85
kern  :warn  : [  347.303203]  really_probe+0x1bb/0x3d4
kern  :warn  : [  347.303214]  driver_probe_device+0xd5/0x10a
kern  :warn  : [  347.303226]  device_driver_attach+0x3c/0x55
kern  :warn  : [  347.303236]  __driver_attach+0x110/0x119
kern  :warn  : [  347.303246]  ? device_driver_attach+0x55/0x55
kern  :warn  : [  347.303255]  bus_for_each_dev+0x73/0xa9
kern  :warn  : [  347.303266]  bus_add_driver+0x12c/0x1de
kern  :warn  : [  347.303276]  driver_register+0x9e/0xd7
kern  :warn  : [  347.303285]  ? 0xffffffffc0856000
kern  :warn  : [  347.303296]  init_tis+0x8d/0x1000 [tpm_tis]
kern  :warn  : [  347.303309]  ? kernel_read+0x59/0x66
kern  :warn  : [  347.303320]  ? ___might_sleep+0x47/0x146
kern  :warn  : [  347.303334]  do_one_initcall+0xa4/0x1c9
kern  :warn  : [  347.303346]  ? slab_pre_alloc_hook+0x31/0x43
kern  :warn  : [  347.303356]  ? kmem_cache_alloc_trace+0xf4/0x106
kern  :warn  : [  347.303369]  do_init_module+0x5b/0x204
kern  :warn  : [  347.303380]  __do_sys_finit_module+0xb4/0xdb
kern  :warn  : [  347.303391]  do_syscall_64+0x4b/0x59
kern  :warn  : [  347.303401]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
kern  :warn  : [  347.303410] RIP: 0033:0x7ead3a5d3199
kern  :warn  : [  347.303419] Code: 00 f3 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 9f 9c 2b 00 f7 d8 64 89 01 48
kern  :warn  : [  347.303435] RSP: 002b:00007fff1e6a0488 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
kern  :warn  : [  347.303446] RAX: ffffffffffffffda RBX: 000057863ff80cb0 RCX: 00007ead3a5d3199
kern  :warn  : [  347.303454] RDX: 0000000000000000 RSI: 000057863e7ece58 RDI: 0000000000000003
kern  :warn  : [  347.303461] RBP: 00007fff1e6a04d0 R08: 0000000000000000 R09: 000057863ff804b0
kern  :warn  : [  347.303469] R10: 0000000000000003 R11: 0000000000000246 R12: 0000000000000000
kern  :warn  : [  347.303477] R13: 000057863ff80b80 R14: 000057863e7ece58 R15: 0000000000000000
kern  :warn  : [  347.303487] Modules linked in: tpm_tis(+) nls_iso8859_1 nls_cp437 vfat fat snd_seq_dummy snd_seq snd_seq_device veth bridge stp llc tun nf_nat_tftp nf_conntrack_tftp nf_nat_ftp nf_conntrack_ftp esp6 ah6 ip6t_REJECT ip6t_ipv6header cmac rfcomm uinput xt_MASQUERADE fuse usbhid iio_trig_sysfs hid_sensor_cros_compat hid_sensor_iio_common industrialio_triggered_buffer kfifo_buf industrialio surface_sam_sid_gpelid tpm_crb surfacepro3_button soc_button_array surface_sam_sid tpm_tis_core btusb btrtl btbcm btintel bluetooth ecdh_generic ecc lzo_rle lzo_compress snd_hda_codec_hdmi zram snd_hda_codec_realtek snd_soc_skl snd_hda_codec_generic joydev snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_hda_intel ipts snd_intel_dspcfg snd_hda_codec ipu3_cio2 ipu3_imgu(C) mwifiex_pcie snd_hwdep snd_hda_core v4l2_fwnode mwifiex mei_me videobuf2_dma_sg videobuf2_memops videobuf2_v4l2 videobuf2_common cfg80211 tpm_vtpm_proxy tablet_mode_switch tpm i915
kern  :warn  : [  347.303603] CR2: ffffb14b40372000
kern  :warn  : [  347.303611] ---[ end trace 5675b83dc3b769d4 ]---
kern  :warn  : [  347.359703] RIP: 0010:tpm_read_log_efi+0x17c/0x1b8 [tpm]
kern  :warn  : [  347.359708] Code: e8 d8 50 a4 c3 eb 41 48 89 83 68 07 00 00 41 8b 55 04 4c 01 f0 41 bc 02 00 00 00 48 89 c7 48 63 0d 02 db 31 c5 48 8d 74 15 10 <f3> a4 48 63 05 f4 da 31 c5 49 01 c6 4c 03 b3 68 07 00 00 4c 89 b3
kern  :warn  : [  347.359713] RSP: 0018:ffffb14b6a813b00 EFLAGS: 00010286
kern  :warn  : [  347.359716] RAX: ffff9c79aa0ec7a9 RBX: ffff9c789fd99000 RCX: fffffffffffff0a1
kern  :warn  : [  347.359719] RDX: 0000000000000a19 RSI: ffffb14b40372000 RDI: ffff9c79aa0ecd80
kern  :warn  : [  347.359721] RBP: ffffb14b40371000 R08: 0000000000000000 R09: 8000000000000063
kern  :warn  : [  347.359724] R10: 000ffffffffff000 R11: 0000000000000001 R12: 0000000000000002
kern  :warn  : [  347.359727] R13: ffff9c7904d98018 R14: 00000000000047a9 R15: ffff9c7c311f2328
kern  :warn  : [  347.359730] FS:  00007ead3aa90740(0000) GS:ffff9c7cdf280000(0000) knlGS:0000000000000000
kern  :warn  : [  347.359733] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kern  :warn  : [  347.359735] CR2: ffffb14b40372000 CR3: 0000000102a04004 CR4: 00000000003606e0
kern  :warn  : [  347.359738] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
kern  :warn  : [  347.359740] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
kern  :err   : [  347.359743] BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:1494
kern  :err   : [  347.359747] in_atomic(): 0, irqs_disabled(): 1, non_block: 0, pid: 8555, name: modprobe
kern  :warn  : [  347.359751] CPU: 1 PID: 8555 Comm: modprobe Tainted: G      D  C        5.4.43-04966-g44ecd9e48613 #21
kern  :warn  : [  347.359754] Hardware name: Microsoft Corporation Surface Book/Surface Book, BIOS 92.3192.768 03.24.2020
kern  :warn  : [  347.359757] Call Trace:
kern  :warn  : [  347.359762]  dump_stack+0x50/0x63
kern  :warn  : [  347.359767]  ___might_sleep+0x12f/0x146
kern  :warn  : [  347.359772]  down_read+0x1c/0x25
kern  :warn  : [  347.359776]  __blocking_notifier_call_chain+0x32/0x63
kern  :warn  : [  347.359779]  do_exit+0x37/0x9c2
kern  :warn  : [  347.359783]  rewind_stack_do_exit+0x17/0x20
kern  :warn  : [  347.359786] RIP: 0033:0x7ead3a5d3199
kern  :warn  : [  347.359789] Code: 00 f3 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 9f 9c 2b 00 f7 d8 64 89 01 48
kern  :warn  : [  347.359794] RSP: 002b:00007fff1e6a0488 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
kern  :warn  : [  347.359797] RAX: ffffffffffffffda RBX: 000057863ff80cb0 RCX: 00007ead3a5d3199
kern  :warn  : [  347.359800] RDX: 0000000000000000 RSI: 000057863e7ece58 RDI: 0000000000000003
kern  :warn  : [  347.359802] RBP: 00007fff1e6a04d0 R08: 0000000000000000 R09: 000057863ff804b0
kern  :warn  : [  347.359805] R10: 0000000000000003 R11: 0000000000000246 R12: 0000000000000000
kern  :warn  : [  347.359807] R13: 000057863ff80b80 R14: 000057863e7ece58 R15: 0000000000000000

On normal chromeos kernel config, oops is treated as panic and when panic happened, chromeos reboots automatically by the following config:

CONFIG_PANIC_ON_OOPS=y
CONFIG_PANIC_TIMEOUT=-1

chrome://flags/ page not working with hardware TPM

It seems that in order to get chrome://flags/ page working, we need to take TPM ownership.
Until we can take the ownership from Windows, use software TPM.

See: https://github.com/imperador/chromefy/issues/40
Related issue getting that page working on SB1: #2

config-general-surface: ACPI error messages appear continuously on dmesg

There is a lot of ACPI error messages on Surface 3. The following messages appear continuously:

kernel: ACPI Error: AE_ERROR, Returned by Handler for [UserDefinedRegion] (20190816/evregio
n-264)
kernel: ACPI Error: Aborting method \_SB.STR2.PAT0 due to previous error (AE_ERROR) (201908
16/psparse-529)

There is no issue on version chromeos-kernel-linux-surface-5.4.24, which uses config-minimal-surface. So, this is maybe a kernel config issue.

no vmlinuz in syslinux/ while applying kernel

the only vmlinuz i found is under /boot with two vmlinuz files vmlinuz and vmlinuz-4.14.157

I'm using Kernel version: chromeos-v5.4.39.r4076.d37238f2773c3-surface-brunch

GENTOO: built kernel package contains debug files

$ du -sch /build/amd64-generic/packages/sys-kernel/chromeos-kernel-4_19-9999.tbz2
285M	/build/amd64-generic/packages/sys-kernel/chromeos-kernel-4_19-9999.tbz2
285M	total

# (contents of the archive)
$ du -sch *
14M	boot
34M	lib
1019M	usr
1.1G	total

$ du -sch usr/lib/debug/*
546M	usr/lib/debug/boot
473M	usr/lib/debug/lib
1019M	total

Can I build kernel packages without those debug files?

config-minimal-surface: can't sign kernel for secure boot

When I try to sign kernel built with config-minimal-surface by sbsign, I got the following error:

Invalid DOS header magic

Also I can't enroll hash via MokManager.

No issue on kernel built with config-general-surface.