Bug 104834

Summary: does not boot opensuse on fujitsu-siemens platform on cpu t2400-t7200
Product: DRI Reporter: Igor V. Kuznetsov <virex>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs, jani.nikula
Version: XOrg git   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard: ReadyForDev
i915 platform: I945GM i915 features: display/Other
Attachments:
Description Flags
photo of screen on fujitsu-siemens S7110
none
xorg.0.log
none
dmesg log with drm.debug=14
none
dmesg log with a log_bug_len=4M
none
dmesg file
none
kernel log from journalctl -k
none
All logs from journalctl -a none

Description Igor V. Kuznetsov 2018-01-29 12:45:47 UTC
Created attachment 137020 [details]
photo of screen on fujitsu-siemens S7110

Laptops Fujitsu-Siemens S7110 and E8110 Does not boot on Opensuse 4.14.14.1-vanilla kernel.
Comment 1 Jani Nikula 2018-01-29 17:43:47 UTC
Is this a regression? Did some earlier kernel work?

Please add drm.degug=14 module parameter and try to get dmesg out of the system.
Comment 2 Igor V. Kuznetsov 2018-01-30 05:48:32 UTC
Created attachment 137045 [details]
xorg.0.log
Comment 3 Igor V. Kuznetsov 2018-01-30 05:52:50 UTC
these laptops work fine on opensuse 13.1 on kernel 3.12.67.

i try to boot with a drm.debug=14, but cant find dmesg or dont know how get it.

But i found interesting in Xorg.0.log (i attached this file)


[    52.376] (II) Loading sub module "fb"
[    52.376] (II) LoadModule: "fb"
[    52.376] (II) Loading /usr/lib/xorg/modules/libfb.so
[    52.377] (II) Module fb: vendor="X.Org Foundation"
[    52.377] 	compiled for 1.19.6, module version = 1.0.0
[    52.377] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    52.377] (II) UnloadModule: "fbdev"
[    52.377] (II) Unloading fbdev
[    52.377] (II) UnloadSubModule: "fbdevhw"
[    52.377] (II) Unloading fbdevhw
[    52.377] (II) UnloadModule: "vesa"
[    52.377] (II) Unloading vesa
[    52.377] (==) Depth 24 pixmap format is 32 bpp
[    52.377] Require OpenGL version 2.1 or later.
[    52.377] (EE) modeset(0): Failed to initialize glamor at ScreenInit() time.
[    52.377] (EE) 
Fatal server error:
[    52.377] (EE) AddScreen/ScreenInit failed for driver 0
[    52.377] (EE) 
[    52.377] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    52.377] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    52.377] (EE) 
[    52.408] (EE) Server terminated with error (1). Closing log file.
Comment 4 Igor V. Kuznetsov 2018-01-30 05:57:03 UTC
i made a video how it is booting and after that blinking the screen https://youtu.be/BJplHiuHDCw
Comment 5 Jani Nikula 2018-01-30 08:51:41 UTC
(In reply to Igor V. Kuznetsov from comment #3)
> i try to boot with a drm.debug=14, but cant find dmesg or dont know how get
> it.

man dmesg
Comment 6 Igor V. Kuznetsov 2018-01-31 12:38:10 UTC
Created attachment 137086 [details]
dmesg log with drm.debug=14

dmesg log with drm.debug=14
Comment 7 Elizabeth 2018-02-01 21:31:44 UTC
dmesg is incomplete, could you please add in grub log_bug_len=4M(or bigger as needed), to get the full boot.
Comment 8 Igor V. Kuznetsov 2018-02-02 12:35:37 UTC
Created attachment 137128 [details]
dmesg log with a log_bug_len=4M
Comment 9 Igor V. Kuznetsov 2018-02-02 12:36:26 UTC
I tryed also boot from tumbleweed kde live. Same problem
Comment 10 Elizabeth 2018-02-02 15:45:02 UTC
Guess this has something to do:
[   59.840335] [drm:intel_get_load_detect_pipe [i915]] no pipe available for load-detect
Could you please attach kern.log?
Comment 11 Igor V. Kuznetsov 2018-02-03 03:27:44 UTC
I uploaded all /var/log/* with a folders into a clowd disk.yandex.ru: 

https://yadi.sk/d/oHq35uZF3S3stD

PS: I cant find kern.log maybe it in new journal
Comment 12 Igor V. Kuznetsov 2018-02-16 13:17:58 UTC
I had trying to boot opensuse tumbleweed 32 bit kde live iso with the same problem on another fujitsu laptop, and uploaded all logs into yandex disk link is https://yadi.sk/d/ahfNZaod3SU7Ly
Comment 13 Igor V. Kuznetsov 2018-02-16 13:18:42 UTC
Created attachment 137390 [details]
dmesg file
Comment 14 Igor V. Kuznetsov 2018-02-16 13:19:24 UTC
Created attachment 137391 [details]
kernel log from journalctl -k
Comment 15 Igor V. Kuznetsov 2018-02-16 13:20:36 UTC
Created attachment 137392 [details]
All logs from journalctl -a
Comment 16 Jani Saarinen 2018-03-29 07:10:54 UTC
First of all. Sorry about spam.
This is mass update for our bugs. 

Sorry if you feel this annoying but with this trying to understand if bug still valid or not.
If bug investigation still in progress, please ignore this and I apologize!

If you think this is not anymore valid, please comment to the bug that can be closed.
If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Comment 17 Jani Saarinen 2018-04-24 06:52:37 UTC
Jani, any advice here to proceed?
Comment 18 Lakshmi 2018-09-11 08:22:17 UTC
Sorry for the delay...

Reporter, do you still have the issue?

Please try to reproduce the issue using drm-tip (https://cgit.freedesktop.org/drm-tip) and kernel parameters drm.debug=0x1e log_buf_len=4M, and if the problem persists attach the full dmesg from boot.

This will help us to set the right priority and speed up the investigation.
Comment 19 Igor V. Kuznetsov 2018-09-12 08:11:14 UTC
Sorry for not answering, I fogot about this report on bugs.freedesktop.org. I also send report to bugzilla.opensuse.org.

About problem. After several kernel updates problem is gone.
Comment 20 Lakshmi 2018-10-04 18:19:23 UTC
(In reply to Igor V. Kuznetsov from comment #19)
> Sorry for not answering, I fogot about this report on bugs.freedesktop.org.
> I also send report to bugzilla.opensuse.org.
> 
> About problem. After several kernel updates problem is gone.

Thanks for your feedback. Closing this bug.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.