Bug 200315
| Summary: | [Regression] Wired network does not come back after reboot | ||
|---|---|---|---|
| Product: | Networking | Reporter: | Nícholas Lima de Souza Silva (nicholaslima.rw) |
| Component: | Other | Assignee: | Stephen Hemminger (stephen) |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | hkallweit1 |
| Priority: | P1 | ||
| Hardware: | x86-64 | ||
| OS: | Linux | ||
| Kernel Version: | 4.17.2 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Attachments: | It's a log from journalctl NetworkManager | ||
*** This bug has been marked as a duplicate of bug 200195 *** This issue seems to be different from the linked one, the other was about issues after resume from suspend. Please provide full dmesg output of 1. a fresh boot (where network works) 2. a reboot (where network doesn't work) Does network work after resume from suspend-to-ram (if supported on your system)? Does kernel version 4.17.13 fix the issue? (In reply to Heiner Kallweit from comment #2) > This issue seems to be different from the linked one, the other was about > issues after resume from suspend. > > Please provide full dmesg output of > 1. a fresh boot (where network works) > 2. a reboot (where network doesn't work) > > Does network work after resume from suspend-to-ram (if supported on your > system)? > > Does kernel version 4.17.13 fix the issue? The issue was fixed on the kernel version 4.17.11 |
Created attachment 276937 [details] It's a log from journalctl NetworkManager Only difference is using kernel 4.17.2 vs kernel 4.16.15 When using 4.17.2, the network does not work after rebooting. With 4.16.15 it works as expected. Complementing: The wired connection doesn't work if I choose to reboot, but It does work if I power it off and on again.