[Bug 1888090] Re: Frequent Kernel panic in 5.4.0-40 but not 5.4.0-29 on Gemini Lake cpu and r8169r

2020-10-04 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888090

[Bug 1888090] Re: Frequent Kernel panic in 5.4.0-40 but not 5.4.0-29 on Gemini Lake cpu and r8169r

2020-08-05 Thread Jeroen Baten
IMHO kernel version 5.4.0-40 should be deleted with the highest prejudice. Never before have I experienced 3 kernel panics in one day and a few after that. This thing should have never left Canonical quality control for an LTS system. And I have been running Ubuntu since the first release. Jul

[Bug 1888090] Re: Frequent Kernel panic in 5.4.0-40 but not 5.4.0-29 on Gemini Lake cpu and r8169r

2020-07-28 Thread Akom
I've been testing it for the past 3 days and no crashes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888090 Title: Frequent Kernel panic in 5.4.0-40 but not 5.4.0-29 on Gemini Lake cpu and

[Bug 1888090] Re: Frequent Kernel panic in 5.4.0-40 but not 5.4.0-29 on Gemini Lake cpu and r8169r

2020-07-27 Thread Kai-Heng Feng
Can you please test 5.4.0-42.46? Thanks! ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888090 Title: Frequent Kernel panic in

[Bug 1888090] Re: Frequent Kernel panic in 5.4.0-40 but not 5.4.0-29 on Gemini Lake cpu and r8169r

2020-07-19 Thread Akom
Things I also tried: * Disabled onboard LAN (r8169) and used a PCIe---(adapter)--->PCI--->Linksys 10/100 NIC (tulip driver). * Disabled all CPU/Chipset features in the BIOS, all APCI/power savings, sleep states, turbo, etc. (Still crashed). -- You received this bug notification because you