Bug #80

Screen garbled in Seabios, does not boot, Kernel panic (X60)

Added by Daniel Kulesz over 2 years ago. Updated about 2 years ago.

Status:NewStart date:10/15/2016
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

I tried updating from Coreboot-4.4 to current HEAD on my Thinkpad X60. The build went fine, but afterwards:

  • screen was partly disorted / garbled (big green artifacts in the bottom part)
  • first attempt to boot resulted in kernel panic
  • could get machine to boot only after rebooting and then it booted normally

Downgraded now to 4.4, and things are working okay again.

config.txt Magnifier (18.2 KB) Daniel Kulesz, 10/15/2016 06:41 PM

IMG_20161118_161249.jpg (177 KB) Daniel Kulesz, 11/18/2016 03:41 PM

IMG_20161118_132934.jpg (192 KB) Daniel Kulesz, 11/18/2016 03:42 PM

IMG_20161118_142310.jpg (168 KB) Daniel Kulesz, 11/18/2016 03:42 PM

IMG_20161118_161220.jpg (127 KB) Daniel Kulesz, 11/18/2016 03:42 PM

IMG_20161118_161249.jpg (177 KB) Daniel Kulesz, 11/18/2016 03:42 PM

cbfs.txt Magnifier (1020 Bytes) Daniel Kulesz, 04/14/2017 01:02 PM

config.short.txt Magnifier (444 Bytes) Daniel Kulesz, 04/14/2017 01:02 PM

coreboot_console.txt Magnifier (36 Bytes) Daniel Kulesz, 04/14/2017 01:02 PM

config.txt Magnifier (18.8 KB) Daniel Kulesz, 04/14/2017 01:02 PM

coreboot_timestamps.txt Magnifier (39 Bytes) Daniel Kulesz, 04/14/2017 01:02 PM

payload_config.txt Magnifier (1.59 KB) Daniel Kulesz, 04/14/2017 01:02 PM

revision.txt Magnifier (173 Bytes) Daniel Kulesz, 04/14/2017 01:02 PM

kernel_log.txt Magnifier (61.1 KB) Daniel Kulesz, 04/14/2017 01:02 PM

rom_checksum.txt Magnifier (53 Bytes) Daniel Kulesz, 04/14/2017 01:02 PM

History

#1 Updated by Daniel Kulesz over 2 years ago

I had the same issue with the official 4.5 release. Then I switched off the following option:

Display => Keep VESA framebuffer

Since then, everything is back to normal. However, in 4.4 it used to work with the option enabled (just double-checked), so I would consider this a regression.

#2 Updated by Arthur Heymans over 2 years ago

Could you see if commit 9c5fc62f9 "nb/i945/gma.c: use IS_ENABLED instead of #if, #endif" was in your git tree that you flashed? This breaks native graphic init, but is fixed in https://review.coreboot.org/#/c/17075/ .

#3 Updated by Daniel Kulesz over 2 years ago

Sorry, didn't see your comment. Since the commit is merged, I will try with the current master and report back.

#4 Updated by Daniel Kulesz over 2 years ago

I retried in master as of cd2afc0df034670a83479aded514b22b99124cf5. Here is what changed:

  • again, first attempt to boot after flashing resulted in kernel panic (blinking scroll lock led)
  • the issue that the device does not boot up at the first time got better. Lockup during boot happens only occasionally but is not easily reproducible.
  • however, the device sometimes does not init correctly (empty screen, backlight on)
  • when using the "Keep VESA framebuffer" option, the screen is still garbled during bootup, and also when booting into text-based Payloads such as meminfo or memtest86+. Memtest86+ itself does not report any memory issues (when running coreboot without the VESA option since no output is visible when activated).

I am attaching pictures for some of the symptoms.

#7 Updated by Daniel Kulesz over 2 years ago

Btw.: It's a X60s, not a regular X60.

#8 Updated by Arthur Heymans over 2 years ago

I don't seem to have these issues on my x60. Linux can be unhappy if gpu was not initiated properly.

Could you include a cblog?
Would also be nice if you could bisect this issue, if you say this is a regression.

#9 Updated by Daniel Kulesz about 2 years ago

I tried on current master, and there the issue is still present. I am trying to recover from this issue - until then, I will not be able to provide cblog.

#10 Updated by Daniel Kulesz about 2 years ago

Here are the logs.

#11 Updated by Daniel Kulesz about 2 years ago

One more thing I noticed in the VESA "broken" Mode:

If I hit "Esc" in Seabios after cold boot and choose the boot device, the system will always hang. If I do not hit Esc but let it continue booting, the Linux kernel will succeed in initializing the graphics most of the time. Some timing issue?

Also available in: Atom PDF