Peppermint OS Community Forum

Support => Installation => Topic started by: Pikolo on August 19, 2017, 06:31:54 am

Title: What is Peppermint doing differently?
Post by: Pikolo on August 19, 2017, 06:31:54 am
I've got a new laptop, one with a Kabylake i7, a GTX 1050Ti and an SSD. From Dell, albeit it came with Windows 10 preinstalled, cause their Linux selection didn't include anything alike in it's price range. So far, Peppermint has been the only distro to work perfectly OOtB, and I'm wondering why.

On other distro's, I get this warning while booting:
(https://i.imgur.com/PnVeL4b.jpg)

Peppermint 8 doesn't get it(or doesn't show it).
KDE Neon, also based on Ubuntu 16.04, had trouble installing the bootloader(so I made Peppermint's bootloader the chief one), and the graphical server malfunctions, so that every boot I have to switch to a tty and run startx to get a graphical shell.
On Solus 3, which I hoped would avoid these problems because it's a rolling release, the graphical server also malfunctions, except there I can't even get to a tty, cause Ctrl+Alt+F1 doesn't work.
On both Peppermint 8 and KDE Neon I installed proprietary Nvidia drivers, and set them to run on the Intel card, because I currently need long better life rather than GPU performance, but it didn't change anything on both distributions

So, what do these errors mean? And how does Peppermint get past them?
I just found a bug from yesterday showing something similar: https://bugzilla.freedesktop.org/show_bug.cgi?id=102295
I wonder if it's attached to the fact that Peppermint8 is installed to the HDD(hence it loads slower, and doesn't probe lspcon before it's ready), while KDE Neon is installed to the SSD, and the live CD of Solus was booted from a USB3... Hopefully it'll be fixed sooner rather than later :/

Code: [Select]
pshem@PiDell:~$ inxi -Fz
System:    Host: PiDell Kernel: 4.10.0-32-generic x86_64 (64 bit)
           Desktop: KDE Plasma 5.8.7 Distro: neon 16.04 xenial
Machine:   System: Dell (portable) product: Inspiron 15 7000 Gaming
           Mobo: Dell model: 065C71 v: A00
           Bios: Dell v: 01.00.05 date: 03/01/2017
CPU:       Quad core Intel Core i7-7700HQ (-HT-MCP-) cache: 6144 KB
           clock speeds: max: 3800 MHz 1: 899 MHz 2: 899 MHz 3: 899 MHz
           4: 899 MHz 5: 899 MHz 6: 899 MHz 7: 899 MHz 8: 899 MHz
Graphics:  Card-1: Intel Device 591b
           Card-2: NVIDIA Device 1c8c
           Display Server: X.Org 1.19.3 drivers: (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.00hz
           GLX Renderer: Mesa DRI Intel Kabylake GT2
           GLX Version: 3.0 Mesa 17.0.7
Audio:     Card Intel Device a171 driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.10.0-32-generic   
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169
           IF: enp2s0 state: down mac: <filter>
           Card-2: Intel Wireless 3165 driver: iwlwifi
           IF: wlp3s0 state: up mac: <filter>
Drives:    HDD Total Size: 1264.8GB (3.2% used)
           ID-1: /dev/sda model: Micron_1100_SATA size: 256.1GB
           ID-2: /dev/sdb model: TOSHIBA_MQ01ABD1 size: 1000.2GB
           ID-3: USB /dev/sdc model: USB_Flash_Disk size: 8.5GB
Partition: ID-1: / size: 130G used: 12G (10%) fs: ext4 dev: /dev/sda4
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 48.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 214 Uptime: 6 min Memory: 959.6/15911.3MB
           Client: Shell (bash) inxi: 2.2.35
Title: Re: What is Peppermint doing differently?
Post by: PCNetSpec on August 19, 2017, 06:43:39 am
Have you tried disabling hyperthreading in the BIOS ?

If that works, try installing the latest intel microcode (20170707), then re-enabling hyperthreading...

There's instructions how to do this on Ubuntu 16.04 based distros here:
https://forum.peppermintos.com/index.php/topic,5763.0.html
but for other distros you'll have to ask them.
Title: Re: What is Peppermint doing differently?
Post by: Pikolo on August 19, 2017, 07:35:39 am
Luckily I seem to have a firmware update(http://www.dell.com/support/home/pl/pl/pldhs1/drivers/driversdetails?driverId=9R7T4&fileId=3690868011&osCode=BIOSA&productCode=inspiron-15-7567-laptop&languageCode=po&categoryId=BI (http://www.dell.com/support/home/pl/pl/pldhs1/drivers/driversdetails?driverId=9R7T4&fileId=3690868011&osCode=BIOSA&productCode=inspiron-15-7567-laptop&languageCode=po&categoryId=BI)) that mentions updating the microcode, just from 28/06/17, ie. 2 days after the ArsTechinca article :)
Hopefully it solves the issues ;)
Thank you bringing that to my attention 8)
Title: Re: What is Peppermint doing differently?
Post by: Pikolo on August 19, 2017, 04:06:15 pm
The installation went smoothly, but it didn't change anything :/
After reading around, it looks like the ACPI Errors are typical false positives on Dell machines, hence I assume the problems come from lspcon_init
Title: Re: What is Peppermint doing differently?
Post by: PCNetSpec on August 20, 2017, 08:09:01 am
Well we're doing nothing 'special' .. what kernel do the others use that are failing ?
Title: Re: What is Peppermint doing differently?
Post by: VinDSL on August 20, 2017, 01:28:06 pm
Well we're doing nothing 'special' ..

We tend to enjoy the company of those who are genuine and humble, but really -- 'nothing special'?

Don't be too modest of your skills and don't belittle what you're capable of, PCNoSleep...  ;D
Title: Re: What is Peppermint doing differently?
Post by: Pikolo on August 20, 2017, 03:30:09 pm
Well we're doing nothing 'special' .. what kernel do the others use that are failing ?
KDE Neon uses the exact same kernel as Peppermint - both distro's have Ubuntu 16.04 under the hood. From my understanding Solus uses the 4.9 branch in the default install, but they also package 4.12 if you want to be bleeding edge.

Of interest is something peculiar: searching for "lspcon_init" yields <10 results! https://duckduckgo.com/?q=%22lspcon_init%22&t=canonical&ia=web (https://duckduckgo.com/?q=%22lspcon_init%22&t=canonical&ia=web)
All of them but one are from this year, and one(from pastebinhttps://pastebin.com/T1BnMqfG (https://pastebin.com/T1BnMqfG)), shows the same errors on the same PC model(the host is called Inspiron-15-Gaming, the name the installer suggested)

Intel DRM mailing lists suggests it's a problem with display port, and my understanding is that this is the port through which the screen is connected. These have been merged for 4.13.rc5(https://github.com/torvalds/linux/commit/28904eeced2c6cf6d315c675e79e1700ef7507ac (https://github.com/torvalds/linux/commit/28904eeced2c6cf6d315c675e79e1700ef7507ac)), so I'll get them in the next time the kernel series is bumped, if 17.10 will use the 4.13 kernel.

Running the same command as the guy from pastebin did on KDE Neon yields:
Code: [Select]
pshem@PiDell:~$ journalctl --dmesg --pri=3
-- Logs begin at Sat 2017-08-19 21:12:07 CEST, end at Sun 2017-08-20 21:17:01 CEST. --
Aug 19 21:12:07 PiDell kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20160930/dswload-210)
Aug 19 21:12:07 PiDell kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20160930/psobject-227)
Aug 19 21:12:07 PiDell kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_OEMBD) while loading table (20160930/tbxfload-228)
Aug 19 21:12:07 PiDell kernel: ACPI Error: 1 table load failures, 10 successful (20160930/tbxfload-246)
Aug 19 21:12:07 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ee2000000040110a
Aug 19 21:12:07 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef1ffc0 MISC 7880010086
Aug 19 21:12:07 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503169923 SOCKET 0 APIC 0 microcode 5e
Aug 19 21:12:07 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 7: ee2000000040110a
Aug 19 21:12:07 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef1ce40 MISC 47880010086
Aug 19 21:12:07 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503169923 SOCKET 0 APIC 0 microcode 5e
Aug 19 21:12:07 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 8: ee2000000040110a
Aug 19 21:12:07 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef1ff40 MISC 7880010086
Aug 19 21:12:07 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503169923 SOCKET 0 APIC 0 microcode 5e
Aug 19 21:12:07 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 9: ee2000000040110a
Aug 19 21:12:07 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef1ff00 MISC 3880010086
Aug 19 21:12:07 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503169923 SOCKET 0 APIC 0 microcode 5e
Aug 19 21:12:07 PiDell kernel: [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
Aug 19 21:12:07 PiDell kernel: [drm:intel_ddi_init [i915]] *ERROR* LSPCON init failed on port B
Aug 19 21:12:08 PiDell kernel: sd 2:0:0:0: [sdc] No Caching mode page found
Aug 19 21:12:08 PiDell kernel: sd 2:0:0:0: [sdc] Assuming drive cache: write through
Aug 19 21:12:08 PiDell kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xfed40080-0xfed40fff]
Aug 19 21:34:38 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ee2000000040110a
Aug 19 21:34:38 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef20080 MISC 3880000086
Aug 19 21:34:38 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503171278 SOCKET 0 APIC 0 microcode 5e
Aug 19 21:34:38 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 7: ee2000000040110a
Aug 19 21:34:38 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef200c0 MISC 3880000086
Aug 19 21:34:38 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503171278 SOCKET 0 APIC 0 microcode 5e
Aug 19 21:34:38 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 8: ee2000000040110a
Aug 19 21:34:38 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef20000 MISC 3880000086
Aug 19 21:34:38 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503171278 SOCKET 0 APIC 0 microcode 5e
Aug 19 21:34:38 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 9: ee2000000040110a
Aug 19 21:34:38 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef20040 MISC 3880000086
Aug 19 21:34:38 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503171278 SOCKET 0 APIC 0 microcode 5e
Aug 19 21:47:50 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ee2000000040110a
Aug 19 21:47:50 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef20080 MISC 3880000086
Aug 19 21:47:50 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503172070 SOCKET 0 APIC 0 microcode 5e
Aug 19 21:47:50 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 7: ee2000000040110a
Aug 19 21:47:50 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef200c0 MISC 3880000086
Aug 19 21:47:50 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503172070 SOCKET 0 APIC 0 microcode 5e
Aug 19 21:47:50 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 8: ee2000000040110a
Aug 19 21:47:50 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef20000 MISC 3880000086
Aug 19 21:47:50 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503172070 SOCKET 0 APIC 0 microcode 5e
Aug 19 21:47:50 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 9: ee2000000040110a
Aug 19 21:47:50 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef20040 MISC 3880000086
Aug 19 21:47:50 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503172070 SOCKET 0 APIC 0 microcode 5e
Aug 20 09:58:14 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ee2000000040110a
Aug 20 09:58:14 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef20080 MISC 3880000086
Aug 20 09:58:14 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503215894 SOCKET 0 APIC 0 microcode 5e
Aug 20 09:58:14 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 7: ee2000000040110a
Aug 20 09:58:14 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef200c0 MISC 3880000086
Aug 20 09:58:14 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503215894 SOCKET 0 APIC 0 microcode 5e
Aug 20 09:58:14 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 8: ee2000000040110a
Aug 20 09:58:14 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef20000 MISC 3880000086
Aug 20 09:58:14 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503215894 SOCKET 0 APIC 0 microcode 5e
Aug 20 09:58:14 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 9: ee2000000040110a
Aug 20 09:58:14 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef20040 MISC 3880000086
Aug 20 09:58:14 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503215894 SOCKET 0 APIC 0 microcode 5e
Aug 20 10:18:22 PiDell kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=72464 end=72465) time 4765 us, min 1073, max
Aug 20 10:38:03 PiDell kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=143310 end=143311) time 1796 us, min 1073, ma
Aug 20 11:28:28 PiDell kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=324852 end=324853) time 656 us, min 1073, max
Aug 20 11:29:16 PiDell kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=327702 end=327703) time 552 us, min 1073, max
Aug 20 14:43:34 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ee2000000040110a
Aug 20 14:43:34 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef20080 MISC 3880000086
Aug 20 14:43:34 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503233014 SOCKET 0 APIC 0 microcode 5e
Aug 20 14:43:34 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 7: ee2000000040110a
Aug 20 14:43:34 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef200c0 MISC 3880000086
Aug 20 14:43:34 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503233014 SOCKET 0 APIC 0 microcode 5e
Aug 20 14:43:34 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 8: ee2000000040110a
Aug 20 14:43:34 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef20000 MISC 3880000086
Aug 20 14:43:34 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503233014 SOCKET 0 APIC 0 microcode 5e
Aug 20 14:43:34 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 9: ee2000000040110a
Aug 20 14:43:34 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef20040 MISC 3880000086
Aug 20 14:43:34 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503233014 SOCKET 0 APIC 0 microcode 5e
Aug 20 18:56:00 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ee2000000040110a
Aug 20 18:56:00 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef20080 MISC 3880000086
Aug 20 18:56:00 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503248160 SOCKET 0 APIC 0 microcode 5e
Aug 20 18:56:00 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 7: ee2000000040110a
Aug 20 18:56:00 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef200c0 MISC 3880000086
Aug 20 18:56:00 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503248160 SOCKET 0 APIC 0 microcode 5e
Aug 20 18:56:00 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 8: ee2000000040110a
Aug 20 18:56:00 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef20000 MISC 3880000086
Aug 20 18:56:00 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503248160 SOCKET 0 APIC 0 microcode 5e
Aug 20 18:56:00 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 9: ee2000000040110a
Aug 20 18:56:00 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef20040 MISC 3880000086
Aug 20 18:56:00 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503248160 SOCKET 0 APIC 0 microcode 5e
Aug 20 21:09:37 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ee2000000040110a
Aug 20 21:09:37 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef20080 MISC 3880000086
Aug 20 21:09:37 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503256177 SOCKET 0 APIC 0 microcode 5e
Aug 20 21:09:37 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 7: ee2000000040110a
Aug 20 21:09:37 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef200c0 MISC 3880000086
Aug 20 21:09:37 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503256177 SOCKET 0 APIC 0 microcode 5e
Aug 20 21:09:37 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 8: ee2000000040110a
Aug 20 21:09:37 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef20000 MISC 3880000086
Aug 20 21:09:37 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503256177 SOCKET 0 APIC 0 microcode 5e
Aug 20 21:09:37 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 9: ee2000000040110a
Aug 20 21:09:37 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef20040 MISC 3880000086
Aug 20 21:09:37 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503256177 SOCKET 0 APIC 0 microcode 5e
I'll check if the results are similar on Peppermint 8
Title: Re: What is Peppermint doing differently?
Post by: PCNetSpec on August 20, 2017, 06:03:54 pm
Okay as all of those search results appear to be to do with the i915 (intel graphics) driver .. maybe it's because Peppermint 8 uses Mesa 17.0.2 ?

Might be interesting to see if Peppermint 7 also fails, which used the stock Mesa version from 16.04
Title: Re: What is Peppermint doing differently?
Post by: Pikolo on August 20, 2017, 06:19:27 pm
If anything, it's the other way round, ie. newer drivers fail ??? That would be very bad going forward  :'(
From Neon:
Code: [Select]
pshem@PiDell:~$ inxi -G
Graphics:  Card-1: Intel Device 591b
           Card-2: NVIDIA Device 1c8c
           Display Server: X.Org 1.19.3 drivers: (unloaded: fbdev,vesa) Resolution: 1920x1080@60.00hz
           GLX Renderer: Mesa DRI Intel Kabylake GT2 GLX Version: 3.0 Mesa 17.0.7
Title: Re: What is Peppermint doing differently?
Post by: PCNetSpec on August 20, 2017, 07:25:56 pm
You asked what we do differently .. I can only answer for what we do differently than stock 16.04, and that would be Mesa 17.0.2
(and the kernel/graphics stack from the 16.04-hwe)

Oh, and BTW, even though we're using Mesa 17.0.2 in Peppermint 8 I get:-
Quote
mark@Silver-HP ~ $ inxi -G
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Richland [Radeon HD 8610G]
           Display Server: X.Org 1.19.3 driver: radeon
           Resolution: 1366x768@60.06hz
           GLX Renderer: Gallium 0.4 on AMD ARUBA (DRM 2.49.0 / 4.10.0-32-generic, LLVM 4.0.0)
           GLX Version: 3.0 Mesa 17.1.0

But there's a chance I've installed a later version on my machine (which is FAR from stock now) :-\



BTW, did you ever try disabling hyperthreading in the BIOS .. just to rule in/out the microcode bug ?
Title: Re: What is Peppermint doing differently?
Post by: Pikolo on August 21, 2017, 04:37:52 am
No, I've not tried disabling hyper-threading. I might do it eventually, but it's  basically a no-go - I need 8 threads as this laptop will run multiple VMs, something I need for my studies. I will do it for debugging purposes at some point though.

Ok, here is the journal for comparison:
Code: [Select]
-- Logs begin at pon 2017-08-21 10:23:31 CEST, end at pon 2017-08-21 10:33:23 CEST. --
sie 21 10:23:31 PiDell kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20160930/dswload-210)
sie 21 10:23:31 PiDell kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20160930/psobject-227)
sie 21 10:23:31 PiDell kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_OEMBD) while loading table (20160930/tbxfload-228)
sie 21 10:23:31 PiDell kernel: ACPI Error: 1 table load failures, 10 successful (20160930/tbxfload-246)
sie 21 10:23:31 PiDell kernel: DMAR: DRHD: handling fault status reg 2
sie 21 10:23:31 PiDell kernel: DMAR: [INTR-REMAP] Request device [f0:1f.0] fault index 0 [fault reason 37] Blocked a compatibility form
sie 21 10:23:31 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ee0000000040110a
sie 21 10:23:31 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef1ffc0 MISC 7880010086
sie 21 10:23:31 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503303799 SOCKET 0 APIC 0 microcode 5e
sie 21 10:23:31 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 7: ee0000000040110a
sie 21 10:23:31 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef1ce40 MISC 47880010086
sie 21 10:23:31 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503303799 SOCKET 0 APIC 0 microcode 5e
sie 21 10:23:31 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 8: ee0000000040110a
sie 21 10:23:31 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef1ff40 MISC 7880010086
sie 21 10:23:31 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503303799 SOCKET 0 APIC 0 microcode 5e
sie 21 10:23:31 PiDell kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 9: ee0000000040110a
sie 21 10:23:31 PiDell kernel: mce: [Hardware Error]: TSC 0 ADDR fef1ff00 MISC 3880010086
sie 21 10:23:31 PiDell kernel: mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1503303799 SOCKET 0 APIC 0 microcode 5e
sie 21 10:23:31 PiDell kernel: [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
sie 21 10:23:31 PiDell kernel: [drm:intel_ddi_init [i915]] *ERROR* LSPCON init failed on port B
sie 21 10:23:33 PiDell kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xfed40080-0xfed40fff]
So Peppermint also gets the lspcon_init probe failture, but it supresses showing errors on screen(they flashed for <0,5s) and recovers from it.

@PCNetSpec - your memory was correct, Peppermint 8 does run Mesa 17.0.2 by default:
Code: [Select]
pshem@PiDell ~ $ inxi -G
Graphics:  Card-1: Intel Device 591b
           Card-2: NVIDIA Device 1c8c
           Display Server: X.Org 1.19.3 drivers: (unloaded: fbdev,vesa) Resolution: 1920x1080@60.00hz
           GLX Renderer: Mesa DRI Intel Kabylake GT2 GLX Version: 3.0 Mesa 17.0.2

I'll try installing the newest Mesa from Padoka Stable PPA on Neon, to see if maybe it's a regression in Mesa. If that doesn't work, I'll remove the proprietary nvidia drivers from it and try installing a mainline kernel(I think Ubuntu had .rc's in the kernel PPA)
Title: Re: What is Peppermint doing differently?
Post by: PCNetSpec on August 21, 2017, 02:18:57 pm
I meant disable it temporarily so we could see if that microcode bug is the root cause.

Can't fix/workaround an issue if you won't diagnose it ;)
Title: Re: What is Peppermint doing differently?
Post by: cosmic_orange on February 28, 2018, 12:02:35 pm
I'm sorry for necroing it, but I got exactly the same issue with exactly the same laptop. Pikolo, have you managed to solve the problem? And if yes - a guide is extremely appreciated!

Also, waiting here for a reply from exactly that user might be not the best option, so if administrators/moderators would be so kind to provide me any information on how I could reach this guy out - I'd be more than happy.
A bit of info on solutions I've tried out so far:
- windows fast boot is disabled (yes, I got dual boot)
- tried to disable ACPI in GRUB during boot -- no result
- tried to disable hyperthreading -- no result
- SATA is set to AHCI -- it was set up so even before the problem appeared
- I haven't tried updating the microcode yet, but I've found a bug report at launchpad about quite similar issue. Reporter claims that 'intel-microcde' is installed, though the problem remains. Bug report -> https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763
Title: Re: What is Peppermint doing differently?
Post by: PCNetSpec on February 28, 2018, 02:28:58 pm
Do you know how to add this kernel boot parameter for testing
Code: [Select]
i915.enable_psr=0
?

Source:
https://bugs.freedesktop.org/show_bug.cgi?id=91883

[EDIT]

BTW, Welcome to the forum :)
Title: Re: What is Peppermint doing differently?
Post by: cosmic_orange on March 01, 2018, 07:40:27 am
BTW, Welcome to the forum :)

Thanks!  :)

So, I've tried booting with i915.enable_psr=0 and it gave no result. Just to make sure I did correctly (it's basically the first time I'm dealing with linux problems of level that low): during boot process enter grub, press 'e' on the line with Linux distro installed, append 'Linux' line with 'i915.enable_psr=0', then press 'Ctrl + x'.

Another quite important thing to mention. I was able to boot the system and operates almost flawlessly by through recovery mode. What did was the following:
And that it - system boots up and works fine.

Noticible things here are:
Code: [Select]
Graphics:  Card-1: Intel Device 591b bus-ID: 00:02.0
           Card-2: NVIDIA Device 1c8c bus-ID: 01:00.0
           Display Server: X.Org 1.19.5 drivers: vesa (unloaded: fbdev) Resolution: 1920x1080@0.00hz
           GLX Renderer: llvmpipe (LLVM 5.0, 256 bits) GLX Version: 3.0 Mesa 17.2.8 Direct Rendering: Yes
Obviously, if I reboot the system completely and select normal boot instead of this way, the problem still persists. I tried this out with both proprietary nvidia and Mesa installed - the difference is that nvidia drivers fail to load after performing 'clean', though the system still worked just the same. Other graphics limitations after booting like that is that I can't connect external display through HDMI port (laptop see anything connected, though monitor wakes up and shows its own screensave thing) and I can't control display brightness level - neither using hotkeys nor from menu (I just couldn't find it where it supposedly should be).

Here are full specs of my system (sorry for no spoiler - for some reason code formatting is suppressed down to scrollable 2 lines view window under the spoiler):
Code: [Select]
System:    Host: orange Kernel: 4.13.0-36-generic x86_64 (64 bit gcc: 5.4.0) Desktop: Xfce 4.12.3 (Gtk 2.24.28)
           Distro: Ubuntu 16.04 xenial
Machine:   System: Dell (portable) product: Inspiron 15 7000 Gaming
           Mobo: Dell model: 065C71 v: X02 Bios: Dell v: 01.00.03 date: 01/10/2017
CPU:       Quad core Intel Core i7-7700HQ (-HT-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 22464
           clock speeds: max: 2800 MHz 1: 2800 MHz 2: 2800 MHz 3: 2800 MHz 4: 2800 MHz 5: 2800 MHz 6: 2800 MHz
           7: 2800 MHz 8: 2800 MHz
Graphics:  Card-1: Intel Device 591b bus-ID: 00:02.0
           Card-2: NVIDIA Device 1c8c bus-ID: 01:00.0
           Display Server: X.Org 1.19.5 drivers: vesa (unloaded: fbdev) Resolution: 1920x1080@0.00hz
           GLX Renderer: llvmpipe (LLVM 5.0, 256 bits) GLX Version: 3.0 Mesa 17.2.8 Direct Rendering: Yes
Audio:     Card Intel Device a171 driver: snd_hda_intel bus-ID: 00:1f.3 Sound: ALSA v: k4.13.0-36-generic
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: d000 bus-ID: 02:00.0
           IF: enp2s0 state: down mac: <filter>
           Card-2: Intel Wireless 3165 driver: iwlwifi bus-ID: 03:00.0
           IF: wlp3s0 state: up mac: <filter>
Drives:    HDD Total Size: 1525.3GB (26.6% used) ID-1: /dev/sda model: Crucial_CT525MX3 size: 525.1GB
           ID-2: /dev/sdb model: TOSHIBA_MQ02ABD1 size: 1000.2GB
Partition: ID-1: / size: 37G used: 6.1G (18%) fs: ext4 dev: /dev/sda5
           ID-2: /home size: 189G used: 24G (13%) fs: ext4 dev: /dev/sda7
           ID-3: swap-1 size: 16.00GB used: 0.00GB (0%) fs: swap dev: /dev/sda6
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 55.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 220 Uptime: 0 min Memory: 507.9/7613.2MB Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.2.35
Title: Re: What is Peppermint doing differently?
Post by: PCNetSpec on March 01, 2018, 08:30:15 am
Are we only talking about error messages at boot but everything works afterwards ?

Apparently the "Namespace lookup failure" has been known for a while now
https://lkml.org/lkml/2016/10/5/299
and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584407
but doesn't seem to cause any adverse effects.

It may be that that the Ubuntu kernel devs (or something in the mesa version we're using) are simply suppressing the messages at boot .. but they're likely still in the logs.
Title: Re: What is Peppermint doing differently?
Post by: cosmic_orange on March 01, 2018, 09:01:53 am
Are we only talking about error messages at boot but everything works afterwards ?

System boots only from recovery mode after launching 'clean'. That's what 'clean' says before launching:
Quote
Continuing will remount your / filesystem in read/write mode and mount any other filesystem defined in /etc/fstab.
Title: Re: What is Peppermint doing differently?
Post by: PCNetSpec on March 01, 2018, 02:52:31 pm
Are you up for an experiment ?

I must point out there are risks attached .. probably small ones, but present all the same .. so you should be in the frame of mind where you'd be okay with a reinstall if things go wrong.
Title: Re: What is Peppermint doing differently?
Post by: cosmic_orange on March 03, 2018, 11:09:54 am
Yes! It's good until only OS partition is affected and it won't damage the hardware. I can backup important data to HDD, then try out doing what's needed.
Title: Re: What is Peppermint doing differently?
Post by: PCNetSpec on March 03, 2018, 06:02:10 pm
Okay boot however you can ..

Now go to

Menu > Preferences > Software & Updates .. and select the "Other Software" tab

On that tab, remove any ticks from boxes that start with
http://ppa.launchpad.net/peppermintos
but make a note of which ones you're unticking.

Once NO repo that starts with
http://ppa.launchpad.net/peppermintos
is ticked, click the "Close" button .. then the "Reload" button when prompted.

When it closes, open a terminal and run:
Code: [Select]
update-usbids
then
Code: [Select]
sudo apt-get update
then
Code: [Select]
sudo apt-get dist-upgrade
Now REBOOT to test

Once rebooted go to

Menu > Preferences > Software & Updates .. and select the "Other Software" tab

On that tab, add back any ticks you removed earlier.

Click the "Close" button .. then the "Reload" button when prompted.

Now post the output from:
Code: [Select]
inxi -Fz