ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]

Bug #1860754 reported by Phuc Minh Cai
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
mesa (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

=== SRU Justification ===
[Impact]
PMIC_OPREGION is required to make GFX works on Bay Trail and Cherry
Trial based tablets.

[Fix]
Enable CONFIG_PMIC_OPREGION.
CONFIG_GPIO_CRYSTAL_COVE needs to be loaded before i915 to control
panel, so change it to builtin.

These configs are aligned with Fedora kernel.

[Test]
The i915 can now kinda work albeit hitting another bug. That's a
different issue though.

[Regression Potential]
Low. These configs only affects Intel-based budget tablets, GFX never
worked.
It's a bit late for Focal so only enable configs in Unstable.

=== Original Bug Report ===

- After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver.
- run udo apt-get install xserver-xorg-video-intel
0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 24 14:29:01 2020
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd]
InstallationDate: Installed on 2020-01-24 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub
 Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. T100HAN
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/18/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: T100HAN.221
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: T100HAN
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: T
dmi.product.name: T100HAN
dmi.product.sku: ASUS-TabletSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

Revision history for this message
Phuc Minh Cai (dcmphuc) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This is correct. Setting i915.modeset=0 will disable the Intel graphics driver so you should not do that.

What are you trying to achieve?

affects: xorg (Ubuntu) → ubuntu
Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Phuc Minh Cai (dcmphuc) wrote :

Hi Daniel,

- At first, I wanted to install Ubuntu 18.04 to my laptop ASUS T100HAN, however it got blank screen with the cursor, I follow instruction to turn off modeset, then it didn't recognize the hard drive (MMC).
- Then I tried to install Ubuntu 19.10 with same turn off modeset. After install, somehow it didn't recognize graphic card > tried to install > then report as mention.
- Now I just checked startup grub2 and noted nomodeset also set. So I tried to remove it, it got blank screen again.
I'm not sure if I did correctly since this is the first time I tried to install in a real machine.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

In theory Ubuntu should support this CPU/GPU without any problem.

Please try removing both "nomodeset" and "i915.modeset=0" and then run:

  sudo update-grub

and then reboot.

If the problem is still not solved, reboot again with "nomodeset" and try to find a historical log from one of the failed boots that had a black screen by running:

  journalctl -b-1 > prevboot.txt

or

  journalctl -b-2 > prevprevboot.txt

and then attach the resulting text file to this bug.

summary: - Graphic driver Intel x5-Z8500
+ ASUS T100HAN boots to a blank screen with a cursor
Revision history for this message
Phuc Minh Cai (dcmphuc) wrote : Re: ASUS T100HAN boots to a blank screen with a cursor

Hi Daniel,

Thank you for quick reply. Please see the attachment.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

See also bug 1838181.

summary: - ASUS T100HAN boots to a blank screen with a cursor
+ ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to
+ submit batchbuffer: Input/output error]
affects: ubuntu → mesa (Ubuntu)
Changed in mesa (Ubuntu):
status: Incomplete → New
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Phuc Minh Cai (dcmphuc) wrote :

Hi Daniel,

What should I do for this issue?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Most likely this is a kernel bug so the next step would be to try some newer or older kernels and see if any of them DO NOT have the same bug. Then hopefully we can identify when things changed.

https://kernel.ubuntu.com/~kernel-ppa/mainline/

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The simplest first test would be to try booting Ubuntu 20.04 from USB:

http://cdimage.ubuntu.com/daily-live/current/

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

On a similar Asus netbook (with an Intel Atom x5-Z8300) I find that Ubuntu 19.10 boots perfectly from USB. Oddly, 20.04 does not. With 20.04 I experience a blank screen more like this bug. To get around it I just avoided the live session. At the 20.04 boot menu, choose 'Install Ubuntu (safe graphics)'. Then it installs and boots successfully (http://cdimage.ubuntu.com/daily-live/20200124/).

So I have the feeling this is close to being fixed in some future live session of 20.04. I wouldn't worry about 19.10 for too long because it will reach end-of-life in July (https://wiki.ubuntu.com/Releases).

I suggest the next step in this bug is for you to follow comment #10 and try 20.04 for yourself.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Changed in mesa (Ubuntu):
status: New → Incomplete
Revision history for this message
Phuc Minh Cai (dcmphuc) wrote :

Hi Daniel,

Thank you for your update.

I have tried to install newest version 20.04. At first, I thought it work since it come to main screen, however cannot control anything for few minutes then it blank screen again. Please see the attachment.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I suspect "cannot control anything for few minutes" is bug 1861648.

If during those few minutes you tried changing VTs etc you might have got a delayed reaction and switched away from the working screen. Try hitting Ctrl+Alt+F1.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/

We may need to enable CONFIG_PMIC_OPREGION to make it fully work.

Revision history for this message
Phuc Minh Cai (dcmphuc) wrote :

Hi Daniel,

I don't know how to enable CONFIG_PMIC_OPREGION. But I installed kernel v5.5 successfully and same issue. Please see the attachment.

Thank you.

Revision history for this message
Phuc Minh Cai (dcmphuc) wrote :

Should I tried kernel v5.5.1? Do I need to uninstall the previous one?
Thank you

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
Phuc Minh Cai (dcmphuc) wrote :

Hi Kai Heng Feng,

Still same black screen. Please see the attachment.

Btw, do you have article about how to check status and enable CONFIG_PMIC_OPREGION? Thank you.

Revision history for this message
Phuc Minh Cai (dcmphuc) wrote :

Hi Kai Heng Feng,

I've tried to install Ubuntu 18.04, also same issue.

Should I continue this bug with version 18.04 or Focal?

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Can you please check the config file under /boot?

Revision history for this message
Phuc Minh Cai (dcmphuc) wrote :

Hi Kai Heng Feng,

Sorry for delaying this for long.

I already check and it already enable but in log file still not. I think there is something not meet with the configuration.

Please see log file.

Thanks and regards,

Revision history for this message
Phuc Minh Cai (dcmphuc) wrote :

Hi Hai Heng Feng,

How are you? Hope you're fine.

I saw it's already release kernel v5.6

Should I try with this kernel?

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
Phuc Minh Cai (dcmphuc) wrote :

Hi Kai Heng Feng,

Thank you very much for quick reply.

I upgrade kernel from your link. However still same issue.

Please see the attachment.

Best regards,
Phuc Minh Cai

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

[+Subscribed Hans]

Hans, I think the issue is caused by:
[drm:intel_dsi_vbt_gpio_init [i915]] *ERROR* Failed to own gpio for panel control

Would be appreciated if you can take a look.

Revision history for this message
Hans de Goede (j-w-r-degoede) wrote :

I have a T100HAN in my personal hw collection, so I just booted up a nightly build of the Fedora 32 workstation livecd on it and that works fine for me. This nightly build is using a 5.6 kernel.

So the 5.6 kernel can work on this hardware. AFAIK Ubuntu, like Fedora puts the i915 driver in the initrd. I guess either a module is missing from the initrd, or there is a module loading ordering issue going on here. The T100HAN uses a Crystal Cove PMIC.

Here are the setting from a couple of relevant Kconfig options which Fedora uses:

CONFIG_INTEL_SOC_PMIC=y
CONFIG_PWM_CRC=y
CONFIG_GPIO_CRYSTAL_COVE=y
CONFIG_PMIC_OPREGION=y
CONFIG_BYTCRC_PMIC_OPREGION=y
CONFIG_CHTCRC_PMIC_OPREGION=y

Note these are all builtin for Fedora, perhaps you can do a test build of an Ubuntu kernel with the same settings?

Also can you attach, or email me the .config Ubuntu is using for building their kernels?

Revision history for this message
Hans de Goede (j-w-r-degoede) wrote :

p.s.

There is another issue with 5.5.y and 5.6 kernels on Cherry Trail hardware, at least with Fedora I'm seeing regular GPU freezes; and specifically on the T100HAN also spontaneous reboots. I've seen the GPU freezes on multiple Cherry Trail devices (these require ssh-ing in and killing gnome-shell to recover from them). I have seen these with both mesa 19.2 and mesa 20.0, so I suspect this is a kernel issue, I still need to investigate these further.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Thank you, Hans.

The difference is CONFIG_GPIO_CRYSTAL_COVE=m, so we need to make it builtin or make it load before i915 in initramfs.

I'll build another kernel for testing.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Hi Phuc Minh Cai,

Please remove the old kernel and test this one:
https://people.canonical.com/~khfeng/lp1860754-3/

Revision history for this message
Phuc Minh Cai (dcmphuc) wrote :

Hi Kai-Heng-Feng,

Thank you very much for your reply.

Previous kernel was removed. I tried to install your new kernel and got same issue. While install new kernel, I found a small error, not sure it would be effected. Below are the details:

sudo dpkg -i *.deb
[sudo] password for srlungaci:
Selecting previously unselected package linux-5.6-headers-5.6.0-8.
(Reading database ... 179408 files and directories currently installed.)
Preparing to unpack linux-5.6-headers-5.6.0-8_5.6.0-8.8_all.deb ...
Unpacking linux-5.6-headers-5.6.0-8 (5.6.0-8.8) ...
Selecting previously unselected package linux-buildinfo-5.6.0-8-generic.
Preparing to unpack linux-buildinfo-5.6.0-8-generic_5.6.0-8.8_amd64.deb ...
Unpacking linux-buildinfo-5.6.0-8-generic (5.6.0-8.8) ...
Selecting previously unselected package linux-headers-5.6.0-8-generic.
Preparing to unpack linux-headers-5.6.0-8-generic_5.6.0-8.8_amd64.deb ...
Unpacking linux-headers-5.6.0-8-generic (5.6.0-8.8) ...
Selecting previously unselected package linux-image-unsigned-5.6.0-8-generic.
Preparing to unpack linux-image-unsigned-5.6.0-8-generic_5.6.0-8.8_amd64.deb ...
Unpacking linux-image-unsigned-5.6.0-8-generic (5.6.0-8.8) ...
Selecting previously unselected package linux-modules-5.6.0-8-generic.
Preparing to unpack linux-modules-5.6.0-8-generic_5.6.0-8.8_amd64.deb ...
Unpacking linux-modules-5.6.0-8-generic (5.6.0-8.8) ...
Selecting previously unselected package linux-modules-extra-5.6.0-8-generic.
Preparing to unpack linux-modules-extra-5.6.0-8-generic_5.6.0-8.8_amd64.deb ...
Unpacking linux-modules-extra-5.6.0-8-generic (5.6.0-8.8) ...
Setting up linux-5.6-headers-5.6.0-8 (5.6.0-8.8) ...
Setting up linux-buildinfo-5.6.0-8-generic (5.6.0-8.8) ...
Setting up linux-headers-5.6.0-8-generic (5.6.0-8.8) ...
Setting up linux-modules-5.6.0-8-generic (5.6.0-8.8) ...
Setting up linux-image-unsigned-5.6.0-8-generic (5.6.0-8.8) ...
I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.4.0-23-generic
I: /boot/initrd.img.old is now a symlink to initrd.img-5.4.0-23-generic
I: /boot/vmlinuz is now a symlink to vmlinuz-5.6.0-8-generic
I: /boot/initrd.img is now a symlink to initrd.img-5.6.0-8-generic
Setting up linux-modules-extra-5.6.0-8-generic (5.6.0-8.8) ...
Processing triggers for linux-image-unsigned-5.6.0-8-generic (5.6.0-8.8) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.6.0-8-generic
modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.6.0-8-generic
Found initrd image: /boot/initrd.img-5.6.0-8-generic
Found linux image: /boot/vmlinuz-5.4.0-23-generic
Found initrd image: /boot/initrd.img-5.4.0-23-generic
Found linux image: /boot/vmlinuz-5.4.0-21-generic
Found initrd image: /boot/initrd.img-5.4.0-21-generic
Adding boot menu entry for UEFI Firmware Settings
done

Please see the log file.

Thank you and have a great day.

Revision history for this message
Hans de Goede (j-w-r-degoede) wrote :

Well the "[drm:intel_dsi_vbt_gpio_init [i915]] *ERROR* Failed to own gpio for panel control" error is gone.

I just noticed you describe the problem as "blank screen with a cursor" , I should have noticed this before. I assume with a cursor you mean a mouse cursor (and not a Linux text console cursor. So you are likely hitting the issue I mentioned before where we hit a GPU freeze and indeed looking closer at the logs that is exactly what is going on:

Apr 09 08:34:55 SrLungACI kernel: i915 0000:00:02.0: GPU HANG: ecode 8:1:85dffffb, in Xorg [938]
Apr 09 08:34:55 SrLungACI kernel: GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.

I have checked and there already is an upstream bug report for this:

https://gitlab.freedesktop.org/drm/intel/-/issues/1605

To which I have added some details about the times when I hit this + a link to this bug.

What might be helpful is if you can configure ssh on your machine, then ssh in while it hangs (that should still work) and do:

sudo cp /sys/class/drm/card0/error i915-crash-dump

And then attach both the dmesg output from that boot as well as the i915-crash-dump file to the upstream bug report:
https://gitlab.freedesktop.org/drm/intel/-/issues/1605

Revision history for this message
Daniel Monteiro (tugapower) wrote :

keep having the same modinfo error on all kernels 5.6.x , running Ubuntu 20.04.

modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory

On kernel 5.5.16 this modinfo error does not appear.

Since the report also have this same message, maybe someone knows something ?

Revision history for this message
Phuc Minh Cai (dcmphuc) wrote :

Hi Hans de Goede,

Thank you very much for your information.

I were able to install OpenSSH server, however I don't know how to do ssh in while it hangs.

Thank you in advance for your help.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

This requires another system to use SSH client to connect to the affected system.

However, that's another bug so I'll just enable those configs for now.

description: updated
Revision history for this message
Phuc Minh Cai (dcmphuc) wrote :

Hi Kai-Heng Feng,

Thank you very much for your information. I will learn more about SSH.

Should I have some action on this or not yet?

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

We'll need help from i915 devs to fix the GFX issue.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 5.8.0-16.17

---------------
linux (5.8.0-16.17) groovy; urgency=medium

  * groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)

  * Miscellaneous Ubuntu changes
    - hio -- Update to use bio_{start,end}_io_acct with 5.8+
    - Enable hio driver
    - [Packaging] Temporarily disable building doc package contents

linux (5.8.0-15.16) groovy; urgency=medium

  * groovy/linux: 5.8.0-15.16 -proposed tracker (LP: #1891177)

  * Miscellaneous Ubuntu changes
    - SAUCE: Documentation: import error c_funcptr_sig_re, c_sig_re (sphinx-
      doc/sphinx@0f49e30c)

linux (5.8.0-14.15) groovy; urgency=medium

  * groovy/linux: 5.8.0-14.15 -proposed tracker (LP: #1891085)

  * Packaging resync (LP: #1786013)
    - [Packaging] update helper scripts

  * msg_zerocopy.sh in net from ubuntu_kernel_selftests failed (LP: #1812620)
    - selftests/net: relax cpu affinity requirement in msg_zerocopy test

  * Fix missing HDMI/DP Audio on an HP Desktop (LP: #1890441)
    - ALSA: hda/hdmi: Add quirk to force connectivity

  * Add initial audio support for Lenovo ThinkStation P620 (LP: #1890317)
    - ALSA: usb-audio: Add support for Lenovo ThinkStation P620

  * Fix IOMMU error on AMD Radeon Pro W5700 (LP: #1890306)
    - PCI: Mark AMD Navi10 GPU rev 0x00 ATS as broken

  * Enlarge hisi_sec2 capability (LP: #1890222)
    - crypto: hisilicon - update SEC driver module parameter

  * Miscellaneous Ubuntu changes
    - [Config] Re-enable signing for ppc64el

 -- Seth Forshee <email address hidden> Tue, 11 Aug 2020 15:32:58 -0500

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.