Bug 192121 - Slow boot kernel 4.9.x and can't reboot normally
Summary: Slow boot kernel 4.9.x and can't reboot normally
Status: RESOLVED OBSOLETE
Alias: None
Product: Drivers
Classification: Unclassified
Component: I2C (show other bugs)
Hardware: x86-64 Linux
: P1 blocking
Assignee: other_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-08 17:43 UTC by Elrondo
Modified: 2018-10-28 01:27 UTC (History)
0 users

See Also:
Kernel Version: 4.10.12
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
Hardware Specs (3.20 KB, text/x-log)
2017-01-08 17:43 UTC, Elrondo
Details

Description Elrondo 2017-01-08 17:43:59 UTC
Created attachment 250811 [details]
Hardware Specs

Hi,

I've strange problem with the 2 last kernels, there is a strange wait time before starting lightdm in 4.8 and 4.9 kernel.
No trace of this waiting time in systemd analyze (same for 4.4,4.8,4.9 kernels)

I'm running SSD, nvidia last dirver and have an FX 8320 CPU

No strange errors in journalctl -b

http://imgh.us/plot_42.svg > Time is the same for all kernel (systemd-analyze)

Video for proof

https://www.youtube.com/watch?v=AY9hOS-ys-M
Comment 1 Elrondo 2017-01-12 19:58:32 UTC
sp5100_tco: I/O address 0x0cd6 already in use >>> Just this change between  kernels

4.4 > No errors about this
4.8 and 4.9 > sp5100_tco: I/O address 0x0cd6 already in use
Comment 2 Elrondo 2017-01-12 20:22:12 UTC
Nothing better when blacklisting the module.

Part of my boot log

janv. 12 21:17:27 elyoake-pc NetworkManager[641]: <info>  [1484252247.3711] manager: startup complete
janv. 12 21:17:41 elyoake-pc kernel: NVRM: Your system is not currently configured to drive a VGA console
janv. 12 21:17:41 elyoake-pc kernel: NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
janv. 12 21:17:41 elyoake-pc kernel: NVRM: requires the use of a text-mode VGA console. Use of other console
janv. 12 21:17:41 elyoake-pc kernel: NVRM: drivers including, but not limited to, vesafb, may result in
janv. 12 21:17:41 elyoake-pc kernel: NVRM: corruption and stability problems, and is not supported.
janv. 12 21:17:41 elyoake-pc kernel: nvidia-modeset: Allocated GPU:0 (GPU-11f8dff6-c5a6-a188-e3c8-714e814e89c4) @ PCI:0000:01:00.0


Why I loose 14 seconds on boot in 4.8 and 4.9
Comment 3 Elrondo 2017-01-14 09:52:27 UTC
Seems related with Nvidia last driver and GeForce GTX 970.... Someone can test this if there is the same delay problem ????
Comment 4 Elrondo 2017-01-18 11:09:51 UTC
Ok.... Same problem with 4.10-rc3.... I simply understand the kernel team don't want to try to solve this bug or answer smething about that. I think there is a lot of problem with kernels created after the 4.4 LTS :(
Comment 5 Elrondo 2017-01-27 06:45:26 UTC
i2c i2c-1: SMBus Timeout!
i2c i2c-1: Failed reset at end of transaction (01)
i2c i2c-1: Failed! (01)
i2c i2c-1: Failed! (01)
i2c i2c-1: Failed! (01)
NetworkManager[664]: <info>  [1485489505.0709] manager: startup complete
i2c i2c-1: SMBus Timeout!
i2c i2c-1: Failed reset at end of transaction (01)
i2c i2c-1: Failed! (01)
i2c i2c-1: Failed! (01)
i2c i2c-1: Failed! (01)

Found it..
Comment 6 Elrondo 2017-01-27 18:28:57 UTC
(In reply to Elrondo from comment #5)
> i2c i2c-1: SMBus Timeout!
> i2c i2c-1: Failed reset at end of transaction (01)
> i2c i2c-1: Failed! (01)
> i2c i2c-1: Failed! (01)
> i2c i2c-1: Failed! (01)
> NetworkManager[664]: <info>  [1485489505.0709] manager: startup complete
> i2c i2c-1: SMBus Timeout!
> i2c i2c-1: Failed reset at end of transaction (01)
> i2c i2c-1: Failed! (01)
> i2c i2c-1: Failed! (01)
> i2c i2c-1: Failed! (01)
> 
> Found it..

For more info: AMD 990FX/SB950 (chipsets), don't know what is the i2c i2c-1
Comment 7 Elrondo 2017-02-01 05:04:47 UTC
Kernel 4.9.6 same prob at boot more errors and now freeze in reboot process, with "no signal" in monitor.

févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-1: SMBus Timeout!
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-1: Failed reset at end of transaction (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-1: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-1: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-1: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-1: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-1: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-1: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-1: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-2: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-2: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-2: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-2: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-2: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-2: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-2: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-2: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-3: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-3: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-3: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-3: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-3: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-3: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-3: Failed! (01)
févr. 01 05:41:37 elyoake-pc kernel: i2c i2c-3: Failed! (01)
Comment 8 Elrondo 2017-02-17 07:52:39 UTC
Same slow boot problem with 4.9.9 but no reboot problem

Just that in error

sp5100_tco: I/O address 0x0cd6 already in use
Comment 9 Elrondo 2017-03-10 08:27:16 UTC
Same bug with 4.9.x and 4.10.x with screen loss at reboot and co.... :(

4.4.x fully okay
Comment 10 Elrondo 2017-03-29 19:52:51 UTC
https://bbs.archlinux.org/viewtopic.php?id=223152

A lot of probs with my motherboard and specially with nvidia cards. No probs with 4.4.
Please solve these probs with 4.9/4.10. No signal with lives of Arch/Manjaro in 4.9 or 4.10 kernel
Comment 11 Elrondo 2017-05-12 05:38:15 UTC
I can believe this bug will be solved inthe future ??????

That's not just me

See this: https://forum.manjaro.org/t/acpi-error-on-laptop-since-kernel-4-9/19834

here too: https://lists.debian.org/debian-kernel/2017/02/msg00285.html
Comment 12 Elrondo 2017-05-23 07:20:33 UTC
Hurra, Blacklist eeprom SOLVE the bug. Now kernel Team has to solve it...

Note You need to log in before you can comment on or make changes to this bug.