Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Sytem totally messsed up after kernel update
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
denijane
n00b
n00b


Joined: 22 Jul 2014
Posts: 14

PostPosted: Tue Dec 04, 2018 12:24 pm    Post subject: Sytem totally messsed up after kernel update Reply with quote

After my update to the latest revision for kernel 4.18.19, my laptop loads for 35 minutes. It's extremely slow and after logging in, the first attempts lasted about 5 minutes, ending with a system freeze and once with the message "Warning, system failed to mount to "/" sysroor" (or something like this I saw it just once). When trying to load another 10 times, I saw multiple dbus and irq errors.

On my last attempt, I did what this link suggested https://forums.gentoo.org/viewtopic-t-1090156.html, i.e.
Code:
ln -s /var/run/dbus /run/dbus   
systemctl start systemd-logind.service


it helped to the extend that I can work with my laptop now, but it occasionally freezes for a minute and one should be really careful not to overload the system (meaning one should work reaally slowly and wait when something freezes).

I tried checking journalctl, dmesg and xorg. There are no obvious errors but for things showing totally weird output (as the long code snipped at the bottom).

The only error I found is this (from Xorg.0.log):
Code:

[   279.488] (EE) [drm] Failed to open DRM device for (null): -2
[   279.488] (EE) [drm] Failed to open DRM device for (null): -2


and in dmesg I have 300 entries of these:
Code:
   85.552252] idma64 idma64.0: Found Intel integrated DMA 64-bit
[   92.297125] pstore: crypto_comp_decompress failed, ret = -22!
[   92.297127] pstore: decompression failed: -22
[   92.297456] pstore: crypto_comp_decompress failed, ret = -22!
[   92.297457] pstore: decompression failed: -22
[   92.297782] pstore: crypto_comp_decompress failed, ret = -22!

And one entry for:
Code:

[   97.718260] thermal thermal_zone3: failed to read out thermal zone (-61)


Apart from that I don't see obvious errors. If anyone is interested, I can also post my journalctl and dmesg here or somewhere.

Any suggestions as to how to debug this and find out what's wrong with my system will be greatly appreciated.



Code:

journalctl -b| tail -150
дек 04 13:44:19 sabayon.local org_kde_powerdevil[1234]: powerdevil: Can't contact ck
дек 04 13:44:19 sabayon.local org_kde_powerdevil[1234]: powerdevil: Scheduling inhibition from ":1.15" "/usr/bin/google-chrome-stable" with cookie 90 and reason "Playing video"
дек 04 13:44:19 sabayon.local org_kde_powerdevil[1234]: powerdevil: Scheduling inhibition from ":1.196" "/usr/bin/google-chrome-stable" with cookie 91 and reason "Playing video"
дек 04 13:44:24 sabayon.local org_kde_powerdevil[1234]: powerdevil: Enforcing inhibition from ":1.15" "/usr/bin/google-chrome-stable" with cookie 90 and reason "Playing video"
дек 04 13:44:24 sabayon.local org_kde_powerdevil[1234]: powerdevil: Added change screen settings
дек 04 13:44:24 sabayon.local org_kde_powerdevil[1234]: powerdevil: Added interrupt session
дек 04 13:44:24 sabayon.local org_kde_powerdevil[1234]: powerdevil: Disabling DPMS due to inhibition
дек 04 13:44:24 sabayon.local org_kde_powerdevil[1234]: powerdevil: Enforcing inhibition from ":1.196" "/usr/bin/google-chrome-stable" with cookie 91 and reason "Playing video"
дек 04 13:44:24 sabayon.local org_kde_powerdevil[1234]: powerdevil: Added interrupt session
дек 04 13:44:24 sabayon.local org_kde_powerdevil[1234]: powerdevil: Can't contact ck
дек 04 13:44:24 sabayon.local org_kde_powerdevil[1234]: powerdevil: Can't contact ck
дек 04 13:44:43 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 48708, resource id: 52428806, major code: 141 (Unknown), minor code: 3
дек 04 13:45:16 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 49611, resource id: 83886141, major code: 141 (Unknown), minor code: 3
дек 04 13:45:16 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 49628, resource id: 71303174, major code: 141 (Unknown), minor code: 3
дек 04 13:45:16 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 49631, resource id: 81788934, major code: 141 (Unknown), minor code: 3
дек 04 13:45:17 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 49639, resource id: 85983268, major code: 141 (Unknown), minor code: 3
дек 04 13:45:17 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 49648, resource id: 90177537, major code: 141 (Unknown), minor code: 3
дек 04 13:45:17 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 49727, resource id: 85983268, major code: 141 (Unknown), minor code: 3
дек 04 13:45:17 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 49739, resource id: 83886141, major code: 141 (Unknown), minor code: 3
дек 04 13:45:17 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 49769, resource id: 83886097, major code: 141 (Unknown), minor code: 3
дек 04 13:45:18 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 49881, resource id: 83886141, major code: 141 (Unknown), minor code: 3
дек 04 13:45:58 sabayon.local org_kde_powerdevil[1234]: powerdevil: Releasing inhibition with cookie  91
дек 04 13:45:58 sabayon.local org_kde_powerdevil[1234]: powerdevil: Releasing inhibition with cookie  90
дек 04 13:45:58 sabayon.local org_kde_powerdevil[1234]: powerdevil: Restoring DPMS features after inhibition release
дек 04 13:45:58 sabayon.local org_kde_powerdevil[1234]: powerdevil: Can't contact ck
дек 04 13:45:58 sabayon.local org_kde_powerdevil[1234]: powerdevil: Can't contact ck
дек 04 13:46:07 sabayon.local org_kde_powerdevil[1234]: powerdevil: Scheduling inhibition from ":1.15" "/usr/bin/google-chrome-stable" with cookie 92 and reason "Playing video"
дек 04 13:46:07 sabayon.local org_kde_powerdevil[1234]: powerdevil: Scheduling inhibition from ":1.198" "/usr/bin/google-chrome-stable" with cookie 93 and reason "Playing video"
дек 04 13:46:12 sabayon.local org_kde_powerdevil[1234]: powerdevil: Enforcing inhibition from ":1.15" "/usr/bin/google-chrome-stable" with cookie 92 and reason "Playing video"
дек 04 13:46:12 sabayon.local org_kde_powerdevil[1234]: powerdevil: Added change screen settings
дек 04 13:46:12 sabayon.local org_kde_powerdevil[1234]: powerdevil: Added interrupt session
дек 04 13:46:12 sabayon.local org_kde_powerdevil[1234]: powerdevil: Disabling DPMS due to inhibition
дек 04 13:46:12 sabayon.local org_kde_powerdevil[1234]: powerdevil: Enforcing inhibition from ":1.198" "/usr/bin/google-chrome-stable" with cookie 93 and reason "Playing video"
дек 04 13:46:12 sabayon.local org_kde_powerdevil[1234]: powerdevil: Added interrupt session
дек 04 13:46:12 sabayon.local org_kde_powerdevil[1234]: powerdevil: Can't contact ck
дек 04 13:46:12 sabayon.local org_kde_powerdevil[1234]: powerdevil: Can't contact ck
дек 04 13:46:26 sabayon.local org_kde_powerdevil[1234]: powerdevil: Releasing inhibition with cookie  93
дек 04 13:46:26 sabayon.local org_kde_powerdevil[1234]: powerdevil: Releasing inhibition with cookie  92
дек 04 13:46:26 sabayon.local org_kde_powerdevil[1234]: powerdevil: Restoring DPMS features after inhibition release
дек 04 13:46:26 sabayon.local org_kde_powerdevil[1234]: powerdevil: Can't contact ck
дек 04 13:46:26 sabayon.local org_kde_powerdevil[1234]: powerdevil: Can't contact ck
дек 04 13:46:26 sabayon.local org_kde_powerdevil[1234]: powerdevil: Scheduling inhibition from ":1.15" "/usr/bin/google-chrome-stable" with cookie 94 and reason "Playing video"
дек 04 13:46:26 sabayon.local org_kde_powerdevil[1234]: powerdevil: Scheduling inhibition from ":1.200" "/usr/bin/google-chrome-stable" with cookie 95 and reason "Playing video"
дек 04 13:46:31 sabayon.local org_kde_powerdevil[1234]: powerdevil: Enforcing inhibition from ":1.15" "/usr/bin/google-chrome-stable" with cookie 94 and reason "Playing video"
дек 04 13:46:31 sabayon.local org_kde_powerdevil[1234]: powerdevil: Added change screen settings
дек 04 13:46:31 sabayon.local org_kde_powerdevil[1234]: powerdevil: Added interrupt session
дек 04 13:46:31 sabayon.local org_kde_powerdevil[1234]: powerdevil: Disabling DPMS due to inhibition
дек 04 13:46:31 sabayon.local org_kde_powerdevil[1234]: powerdevil: Enforcing inhibition from ":1.200" "/usr/bin/google-chrome-stable" with cookie 95 and reason "Playing video"
дек 04 13:46:31 sabayon.local org_kde_powerdevil[1234]: powerdevil: Added interrupt session
дек 04 13:46:31 sabayon.local org_kde_powerdevil[1234]: powerdevil: Can't contact ck
дек 04 13:46:31 sabayon.local org_kde_powerdevil[1234]: powerdevil: Can't contact ck
дек 04 13:47:20 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 51532, resource id: 83886097, major code: 141 (Unknown), minor code: 3
дек 04 13:47:20 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 51545, resource id: 81788934, major code: 141 (Unknown), minor code: 3
дек 04 13:47:20 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 51553, resource id: 71303174, major code: 141 (Unknown), minor code: 3
дек 04 13:47:20 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 51558, resource id: 12582918, major code: 141 (Unknown), minor code: 3
дек 04 13:47:20 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 51567, resource id: 83886141, major code: 141 (Unknown), minor code: 3
дек 04 13:47:20 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 51571, resource id: 83886097, major code: 141 (Unknown), minor code: 3
дек 04 13:47:20 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 51573, resource id: 65011718, major code: 141 (Unknown), minor code: 3
дек 04 13:47:20 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 51578, resource id: 56623110, major code: 141 (Unknown), minor code: 3
дек 04 13:47:20 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 51581, resource id: 54525958, major code: 141 (Unknown), minor code: 3
дек 04 13:47:20 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 51631, resource id: 52428806, major code: 141 (Unknown), minor code: 3
дек 04 13:47:20 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 51635, resource id: 65011718, major code: 141 (Unknown), minor code: 3
дек 04 13:47:20 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 51638, resource id: 58720262, major code: 141 (Unknown), minor code: 3
дек 04 13:47:20 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 51643, resource id: 56623110, major code: 141 (Unknown), minor code: 3
дек 04 13:47:24 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 51731, resource id: 54525958, major code: 141 (Unknown), minor code: 3
дек 04 13:47:25 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 51779, resource id: 52428806, major code: 141 (Unknown), minor code: 3
дек 04 13:47:41 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 51993, resource id: 54525958, major code: 141 (Unknown), minor code: 3
дек 04 13:47:41 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52006, resource id: 65011718, major code: 141 (Unknown), minor code: 3
дек 04 13:47:41 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52017, resource id: 58720262, major code: 141 (Unknown), minor code: 3
дек 04 13:47:41 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52032, resource id: 65011718, major code: 141 (Unknown), minor code: 3
дек 04 13:47:42 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52055, resource id: 83886097, major code: 141 (Unknown), minor code: 3
дек 04 13:47:42 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52123, resource id: 71303174, major code: 141 (Unknown), minor code: 3
дек 04 13:47:42 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52129, resource id: 12582918, major code: 141 (Unknown), minor code: 3
дек 04 13:47:42 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52134, resource id: 83886141, major code: 141 (Unknown), minor code: 3
дек 04 13:47:42 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52137, resource id: 83886097, major code: 141 (Unknown), minor code: 3
дек 04 13:47:42 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52142, resource id: 65011718, major code: 141 (Unknown), minor code: 3
дек 04 13:47:42 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52147, resource id: 56623110, major code: 141 (Unknown), minor code: 3
дек 04 13:47:42 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52149, resource id: 54525958, major code: 141 (Unknown), minor code: 3
дек 04 13:47:42 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52154, resource id: 52428806, major code: 141 (Unknown), minor code: 3
дек 04 13:47:42 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52156, resource id: 50331654, major code: 141 (Unknown), minor code: 3
дек 04 13:47:43 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52265, resource id: 48234502, major code: 141 (Unknown), minor code: 3
дек 04 13:47:44 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52323, resource id: 37748742, major code: 141 (Unknown), minor code: 3
дек 04 13:48:11 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52637, resource id: 46137351, major code: 141 (Unknown), minor code: 3
дек 04 13:48:11 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52666, resource id: 58720262, major code: 141 (Unknown), minor code: 3
дек 04 13:48:11 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52674, resource id: 56623110, major code: 141 (Unknown), minor code: 3
дек 04 13:48:22 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52896, resource id: 54525958, major code: 141 (Unknown), minor code: 3
дек 04 13:48:22 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52903, resource id: 37748742, major code: 141 (Unknown), minor code: 3
дек 04 13:48:22 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52908, resource id: 46137351, major code: 141 (Unknown), minor code: 3
дек 04 13:48:22 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52913, resource id: 48234502, major code: 141 (Unknown), minor code: 3
дек 04 13:48:22 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52916, resource id: 50331654, major code: 141 (Unknown), minor code: 3
дек 04 13:48:22 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 52919, resource id: 52428806, major code: 141 (Unknown), minor code: 3
дек 04 13:49:23 sabayon.local org_kde_powerdevil[1234]: powerdevil: Releasing inhibition with cookie  95
дек 04 13:49:24 sabayon.local org_kde_powerdevil[1234]: powerdevil: Releasing inhibition with cookie  94
дек 04 13:49:24 sabayon.local org_kde_powerdevil[1234]: powerdevil: Restoring DPMS features after inhibition release
дек 04 13:49:24 sabayon.local org_kde_powerdevil[1234]: powerdevil: Can't contact ck
дек 04 13:49:24 sabayon.local org_kde_powerdevil[1234]: powerdevil: Can't contact ck
дек 04 13:49:24 sabayon.local org_kde_powerdevil[1234]: powerdevil: Scheduling inhibition from ":1.15" "/usr/bin/google-chrome-stable" with cookie 96 and reason "Playing video"
дек 04 13:49:24 sabayon.local org_kde_powerdevil[1234]: powerdevil: Scheduling inhibition from ":1.202" "/usr/bin/google-chrome-stable" with cookie 97 and reason "Playing video"
дек 04 13:49:29 sabayon.local org_kde_powerdevil[1234]: powerdevil: Enforcing inhibition from ":1.15" "/usr/bin/google-chrome-stable" with cookie 96 and reason "Playing video"
дек 04 13:49:29 sabayon.local org_kde_powerdevil[1234]: powerdevil: Added change screen settings
дек 04 13:49:29 sabayon.local org_kde_powerdevil[1234]: powerdevil: Added interrupt session
дек 04 13:49:29 sabayon.local org_kde_powerdevil[1234]: powerdevil: Disabling DPMS due to inhibition
дек 04 13:49:29 sabayon.local org_kde_powerdevil[1234]: powerdevil: Enforcing inhibition from ":1.202" "/usr/bin/google-chrome-stable" with cookie 97 and reason "Playing video"
дек 04 13:49:29 sabayon.local org_kde_powerdevil[1234]: powerdevil: Added interrupt session
дек 04 13:49:29 sabayon.local org_kde_powerdevil[1234]: powerdevil: Can't contact ck
дек 04 13:49:29 sabayon.local org_kde_powerdevil[1234]: powerdevil: Can't contact ck
дек 04 13:49:54 sabayon.local org_kde_powerdevil[1234]: powerdevil: Releasing inhibition with cookie  97
дек 04 13:49:54 sabayon.local org_kde_powerdevil[1234]: powerdevil: Releasing inhibition with cookie  96
дек 04 13:49:54 sabayon.local org_kde_powerdevil[1234]: powerdevil: Restoring DPMS features after inhibition release
дек 04 13:49:54 sabayon.local org_kde_powerdevil[1234]: powerdevil: Can't contact ck
дек 04 13:49:54 sabayon.local org_kde_powerdevil[1234]: powerdevil: Can't contact ck
дек 04 13:49:54 sabayon.local org_kde_powerdevil[1234]: powerdevil: Scheduling inhibition from ":1.15" "/usr/bin/google-chrome-stable" with cookie 98 and reason "Playing video"
дек 04 13:49:54 sabayon.local org_kde_powerdevil[1234]: powerdevil: Scheduling inhibition from ":1.204" "/usr/bin/google-chrome-stable" with cookie 99 and reason "Playing video"
дек 04 13:49:58 sabayon.local org_kde_powerdevil[1234]: powerdevil: Releasing inhibition with cookie  99
дек 04 13:49:58 sabayon.local org_kde_powerdevil[1234]: powerdevil: It was only scheduled for inhibition but not enforced yet, just discarding it
дек 04 13:49:58 sabayon.local org_kde_powerdevil[1234]: powerdevil: Releasing inhibition with cookie  98
дек 04 13:49:58 sabayon.local org_kde_powerdevil[1234]: powerdevil: It was only scheduled for inhibition but not enforced yet, just discarding it
дек 04 13:49:58 sabayon.local org_kde_powerdevil[1234]: powerdevil: Scheduling inhibition from ":1.15" "/usr/bin/google-chrome-stable" with cookie 100 and reason "Playing video"
дек 04 13:49:58 sabayon.local org_kde_powerdevil[1234]: powerdevil: Scheduling inhibition from ":1.206" "/usr/bin/google-chrome-stable" with cookie 101 and reason "Playing video"
дек 04 13:49:59 sabayon.local org_kde_powerdevil[1234]: powerdevil: Enforcing inhibition from ":1.15" "/usr/bin/google-chrome-stable" with cookie 98 and reason "Playing video"
дек 04 13:49:59 sabayon.local org_kde_powerdevil[1234]: powerdevil: By the time we wanted to enforce the inhibition it was already gone; discarding it
дек 04 13:49:59 sabayon.local org_kde_powerdevil[1234]: powerdevil: Enforcing inhibition from ":1.204" "/usr/bin/google-chrome-stable" with cookie 99 and reason "Playing video"
дек 04 13:49:59 sabayon.local org_kde_powerdevil[1234]: powerdevil: By the time we wanted to enforce the inhibition it was already gone; discarding it
дек 04 13:50:01 sabayon.local org_kde_powerdevil[1234]: powerdevil: Releasing inhibition with cookie  101
дек 04 13:50:01 sabayon.local org_kde_powerdevil[1234]: powerdevil: It was only scheduled for inhibition but not enforced yet, just discarding it
дек 04 13:50:01 sabayon.local org_kde_powerdevil[1234]: powerdevil: Releasing inhibition with cookie  100
дек 04 13:50:01 sabayon.local org_kde_powerdevil[1234]: powerdevil: It was only scheduled for inhibition but not enforced yet, just discarding it
дек 04 13:50:01 sabayon.local org_kde_powerdevil[1234]: powerdevil: Scheduling inhibition from ":1.15" "/usr/bin/google-chrome-stable" with cookie 102 and reason "Playing video"
дек 04 13:50:01 sabayon.local org_kde_powerdevil[1234]: powerdevil: Scheduling inhibition from ":1.208" "/usr/bin/google-chrome-stable" with cookie 103 and reason "Playing video"
дек 04 13:50:03 sabayon.local org_kde_powerdevil[1234]: powerdevil: Enforcing inhibition from ":1.15" "/usr/bin/google-chrome-stable" with cookie 100 and reason "Playing video"
дек 04 13:50:03 sabayon.local org_kde_powerdevil[1234]: powerdevil: By the time we wanted to enforce the inhibition it was already gone; discarding it
дек 04 13:50:03 sabayon.local org_kde_powerdevil[1234]: powerdevil: Enforcing inhibition from ":1.206" "/usr/bin/google-chrome-stable" with cookie 101 and reason "Playing video"
дек 04 13:50:03 sabayon.local org_kde_powerdevil[1234]: powerdevil: By the time we wanted to enforce the inhibition it was already gone; discarding it
дек 04 13:50:04 sabayon.local org_kde_powerdevil[1234]: powerdevil: Releasing inhibition with cookie  103
дек 04 13:50:04 sabayon.local org_kde_powerdevil[1234]: powerdevil: It was only scheduled for inhibition but not enforced yet, just discarding it
дек 04 13:50:04 sabayon.local org_kde_powerdevil[1234]: powerdevil: Releasing inhibition with cookie  102
дек 04 13:50:04 sabayon.local org_kde_powerdevil[1234]: powerdevil: It was only scheduled for inhibition but not enforced yet, just discarding it
дек 04 13:50:06 sabayon.local org_kde_powerdevil[1234]: powerdevil: Enforcing inhibition from ":1.15" "/usr/bin/google-chrome-stable" with cookie 102 and reason "Playing video"
дек 04 13:50:06 sabayon.local org_kde_powerdevil[1234]: powerdevil: By the time we wanted to enforce the inhibition it was already gone; discarding it
дек 04 13:50:06 sabayon.local org_kde_powerdevil[1234]: powerdevil: Enforcing inhibition from ":1.208" "/usr/bin/google-chrome-stable" with cookie 103 and reason "Playing video"
дек 04 13:50:06 sabayon.local org_kde_powerdevil[1234]: powerdevil: By the time we wanted to enforce the inhibition it was already gone; discarding it
дек 04 13:50:06 sabayon.local org_kde_powerdevil[1234]: powerdevil: Releasing inhibition with cookie  85
дек 04 13:50:06 sabayon.local org_kde_powerdevil[1234]: powerdevil: Can't contact ck
дек 04 13:50:09 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 54273, resource id: 54525958, major code: 141 (Unknown), minor code: 3
дек 04 13:50:09 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 54286, resource id: 46137351, major code: 141 (Unknown), minor code: 3
дек 04 13:50:09 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 54296, resource id: 48234502, major code: 141 (Unknown), minor code: 3
дек 04 13:50:20 sabayon.local plasmashell[1203]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:113: ReferenceError: appIcon is not defined
дек 04 13:50:25 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 54739, resource id: 50331654, major code: 141 (Unknown), minor code: 3
дек 04 13:50:25 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 54836, resource id: 48234502, major code: 141 (Unknown), minor code: 3
дек 04 13:50:26 sabayon.local plasmashell[1203]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 54959, resource id: 46137351, major code: 141 (Unknown), minor code: 3
Back to top
View user's profile Send private message
Muso
l33t
l33t


Joined: 22 Oct 2002
Posts: 985
Location: The Holy city of Honolulu

PostPosted: Tue Dec 04, 2018 12:34 pm    Post subject: Reply with quote

Have you checked this?
_________________
Time is a great teacher, but unfortunately it kills all its pupils.
Back to top
View user's profile Send private message
denijane
n00b
n00b


Joined: 22 Jul 2014
Posts: 14

PostPosted: Tue Dec 04, 2018 1:00 pm    Post subject: Reply with quote

Yes, I checked the Sabayon forum first. But there's nothing similar there, while here the topic I quoted had a similar issue and the dbus step actually helped. This is why I thought maybe here is the better place to post about the problem.
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 22154
Location: here

PostPosted: Tue Dec 04, 2018 1:08 pm    Post subject: Reply with quote

denijane wrote:
Yes, I checked the Sabayon forum first. But there's nothing similar there, while here the topic I quoted had a similar issue and the dbus step actually helped. This is why I thought maybe here is the better place to post about the problem.

If you want post in these forums argument that aren't strict related to gentoo you should post on Unsupported Software.
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
denijane
n00b
n00b


Joined: 22 Jul 2014
Posts: 14

PostPosted: Tue Dec 04, 2018 1:20 pm    Post subject: Reply with quote

I really don't understand how could a distro with gentoo kernel be an "Unsupported software", but put my post wherever you like. I stayed up until 4:30 am to try to find out the problem, I'm utterly miserable because my laptop is pretty unusable, and I simply couldn't care less if you're in some war with Sabayon or not.

I think the Linux community spirit is supposed to mean people helping each other, regardless if they use Gentoo or Sabayon or whatever. But that's obviously just my opinion, so I couldn't care less. I just would really like if some kind soul here could give me a clue what the problem is, because this laptop is my workstation and I need it responsive and working. And I'm desperately needing help in debugging this.
Back to top
View user's profile Send private message
xaviermiller
Administrator
Administrator


Joined: 23 Jul 2004
Posts: 8039
Location: ~Brussels - Belgique

PostPosted: Tue Dec 04, 2018 1:37 pm    Post subject: Reply with quote

Moved from Kernel & Hardware to Unsupported Software.

Hi,

Can you compare the .config from the 2 kernel versions?
Can you rollback to the previous working version?

It seems some module is missing. How did you configure and compile the kernel?
_________________
Kind regards,
Xavier Miller
Back to top
View user's profile Send private message
denijane
n00b
n00b


Joined: 22 Jul 2014
Posts: 14

PostPosted: Tue Dec 04, 2018 3:04 pm    Post subject: Reply with quote

Hi. I can't seem to find any .config in /boot. Tried
Code:
cat /proc/config.gz | gunzip
, but it gave error. Right now whatever I try, I get
Code:
print_req_error: I/0 error, dev sda, sector #number
.
Sometimes even $ls refuses to work with I/0 error. No idea what's going on.
Back to top
View user's profile Send private message
Muso
l33t
l33t


Joined: 22 Oct 2002
Posts: 985
Location: The Holy city of Honolulu

PostPosted: Tue Dec 04, 2018 3:29 pm    Post subject: Reply with quote

Look in /usr/src

Find the old kernel you used and look at the .config in that directory.
_________________
Time is a great teacher, but unfortunately it kills all its pupils.
Back to top
View user's profile Send private message
denijane
n00b
n00b


Joined: 22 Jul 2014
Posts: 14

PostPosted: Tue Dec 04, 2018 4:33 pm    Post subject: Reply with quote

Well this is what I found from /proc/config.gz. In /usr/src I see the kernels, but there are no .config folders.

I'm backing up now, in case bad (or worst) things happen. What I find very troubling is that system takes forever to load, and it seems like it's constantly writing something on the hard. I have a hybrid SSD + SATA and I'm really worried about the hard. Until my update yesterday, I never ever have had problems with it. The laptop is about 7 months old, so that's certainly not normal.

https://bpaste.net/show/f649d8787c0e


Last edited by denijane on Tue Dec 04, 2018 4:46 pm; edited 1 time in total
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 22154
Location: here

PostPosted: Tue Dec 04, 2018 4:35 pm    Post subject: Reply with quote

denijane forum truncate too long message, use wgetpaste for post long message
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
denijane
n00b
n00b


Joined: 22 Jul 2014
Posts: 14

PostPosted: Tue Dec 04, 2018 4:48 pm    Post subject: Reply with quote

Oh OK. I'm sorry about that. I edited the previous post with the bpaste link.
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7191
Location: Saint Amant, Acadiana

PostPosted: Tue Dec 04, 2018 5:02 pm    Post subject: Reply with quote

I/O errors usually mean the hard drive is toast. Why don't you start with booting from an external media and diagnosing the drive.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
denijane
n00b
n00b


Joined: 22 Jul 2014
Posts: 14

PostPosted: Tue Dec 04, 2018 7:34 pm    Post subject: Reply with quote

So far tried to boot Mint and Kali linux from a bootable usb, unsuccessfully. It doesn't start, it stops at the same error:
Code:
ata3: comreset failed error =-16

and processes endlessly trying to start.

I have one Ubunto waiting on the usb and a diagnostic usb that I haven't tried yet, because I wanted first to backup my Home as much as possible from within my otherwise "working" Sabayon.

That's the weird part - that except for the 30 minutes loading time and the random segfault deaths of the system, it otherwise looks like it works. Right now I loaded with acpi=off to see if it makes a difference, it doesn't, but I hope it will buy me time to backup everything.

Anyway, any suggestions for hardware diagnostics I could run are welcome. What I'm pretty sure is that before the update yesterday, my system was working perfectly. There was no sign whatsoever that something was off. Which means that either the update toasted something or that it was incredible coincidence.

I'm pasting the links for the dmesg from my previous system run in case anyone knows what to look for in them:
https://bpaste.net/show/a00510ec7992
And journalctl
https://bpaste.net/show/1109659c8f28
Back to top
View user's profile Send private message
denijane
n00b
n00b


Joined: 22 Jul 2014
Posts: 14

PostPosted: Tue Dec 04, 2018 7:50 pm    Post subject: Reply with quote

Ah, just one more thing I just noticed. My CPU load seems to stay constantly on 100% which is very weird.

It seems that lscpu doesn't know how many threads I have at all! How is this even possible?

Code:

 ~ $ lscpu
Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
CPU(s):              1
On-line CPU(s) list: 0
Thread(s) per core:  1
Core(s) per socket:  1
Socket(s):           1
NUMA node(s):        1
Vendor ID:           GenuineIntel
CPU family:          6
Model:               158
Model name:          Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Stepping:            9
CPU MHz:             1376.511
CPU max MHz:         3800,0000
CPU min MHz:         800,0000
BogoMIPS:            5616.00
Virtualization:      VT-x
L1d cache:           32K
L1i cache:           32K
L2 cache:            256K
L3 cache:            6144K
NUMA node0 CPU(s):   0
Flags:               (edited)


Code:

 $  cat /proc/cpuinfo

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 158
model name      : Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
stepping        : 9
microcode       : 0x84
cpu MHz         : 1204.026
cache size      : 6144 KB
physical id     : 0
siblings        : 1
core id         : 0
cpu cores       : 1
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 22
wp              : yes
flags           : (edited)
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips        : 5616.00
clflush size    : 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:


Code:

$ sudo lshw -C CPU
  *-cpu                     
       description: CPU
       product: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
       vendor: Intel Corp.
       physical id: 47
       bus info: cpu@0
       version: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
       serial: To Be Filled By O.E.M.
       slot: U3E1
       size: 1180MHz
       capacity: 3800MHz
       width: 64 bits
       clock: 100MHz
       capabilities: (edited)
       configuration: cores=4 enabledcores=4 threads=8


Code:

$ nproc
1
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7191
Location: Saint Amant, Acadiana

PostPosted: Tue Dec 04, 2018 8:16 pm    Post subject: Reply with quote

Quote:
So far tried to boot Mint and Kali linux from a bootable usb, unsuccessfully. It doesn't start, it stops at the same error:
Code:
ata3: comreset failed error =-16

and processes endlessly trying to start.


So it has clearly nothing to do with your Sabayon install. But there seems to be a serious issue with your hard drive. Why don't you unplug it and see if you can boot from USB then.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 14056

PostPosted: Wed Dec 05, 2018 2:50 am    Post subject: Reply with quote

denijane wrote:
I really don't understand how could a distro with gentoo kernel be an "Unsupported software", but put my post wherever you like. I stayed up until 4:30 am to try to find out the problem, I'm utterly miserable because my laptop is pretty unusable, and I simply couldn't care less if you're in some war with Sabayon or not.
It is not about a war with Sabayon. If it were, you probably wouldn't be getting any help in this thread. Instead, several people are offering you guidance based on their knowledge of Linux in general.

It is "Unsupported Software" because we don't track what changes Sabayon makes to the Gentoo base that they start from. If they change anything of consequence, and our advice is not adjusted to handle that change, then our advice could be useless, misleading, or outright wrong. For your protection, we want everyone responding to the thread to be very clear that they cannot assume this is a standard Gentoo system that works exactly like they expect Gentoo to work. It might work like standard Gentoo, if your problem is based solely on things Sabayon did not meaningfully modify.

Sabayon's modifications do not need to be wrong or buggy to invalidate our advice. Changes that were perfectly reasonable for their use case can still invalidate assumptions we would rely on when dealing with a standard Gentoo system.
Back to top
View user's profile Send private message
Muso
l33t
l33t


Joined: 22 Oct 2002
Posts: 985
Location: The Holy city of Honolulu

PostPosted: Wed Dec 05, 2018 3:11 am    Post subject: Reply with quote

Hu wrote:
denijane wrote:
I really don't understand how could a distro with gentoo kernel be an "Unsupported software", but put my post wherever you like. I stayed up until 4:30 am to try to find out the problem, I'm utterly miserable because my laptop is pretty unusable, and I simply couldn't care less if you're in some war with Sabayon or not.
It is not about a war with Sabayon. If it were, you probably wouldn't be getting any help in this thread. Instead, several people are offering you guidance based on their knowledge of Linux in general.

It is "Unsupported Software" because we don't track what changes Sabayon makes to the Gentoo base that they start from. If they change anything of consequence, and our advice is not adjusted to handle that change, then our advice could be useless, misleading, or outright wrong. For your protection, we want everyone responding to the thread to be very clear that they cannot assume this is a standard Gentoo system that works exactly like they expect Gentoo to work. It might work like standard Gentoo, if your problem is based solely on things Sabayon did not meaningfully modify.

Sabayon's modifications do not need to be wrong or buggy to invalidate our advice. Changes that were perfectly reasonable for their use case can still invalidate assumptions we would rely on when dealing with a standard Gentoo system.


++

I'm just quoting this for posterity as it was beautifully explained.
_________________
Time is a great teacher, but unfortunately it kills all its pupils.
Back to top
View user's profile Send private message
denijane
n00b
n00b


Joined: 22 Jul 2014
Posts: 14

PostPosted: Wed Dec 05, 2018 11:46 am    Post subject: Reply with quote

Guys, I don't want to fight with anyone. My presumption was that sabayon developers don't change that much in the kernel. It was based on the fact nobody there could (or would) help me with my touchpad/acpi problem with the same laptop before. Maybe I was wrong.

In any case after the update, a laptop which never showed any error or sign of wear (it's 7 months old), now is a toast. Since today it's no longer able to find my hard drive at all. I don't know if it's just a coincidence that it happened after the update or something about the original acpi problem lead to the hard destruction, but it's over. Needless to say I'm too sad to argue about anything.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43546
Location: 56N 3W

PostPosted: Wed Dec 05, 2018 12:25 pm    Post subject: Reply with quote

denijane,

Rule 1 is Presume Nothing. I've learned that the hard way several times. Why presume its a kernel problem?

From your dmesg,
Code:
[    2.914225] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    3.097018] ata3.00: ATA-10: ST1000LX015-1U7172, SDM1, max UDMA/133
[    3.097021] ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[    3.296561] ata3.00: configured for UDMA/133
[    3.296820] scsi 2:0:0:0: Direct-Access     ATA      ST1000LX015-1U71 SDM1 PQ: 0 ANSI: 5
[    3.297099] sd 2:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[    3.297102] sd 2:0:0:0: [sda] 4096-byte physical blocks
[    3.297113] sd 2:0:0:0: [sda] Write Protect is off
[    3.297116] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    3.297131] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.297195] sd 2:0:0:0: Attached scsi generic sg0 type 0
[    3.302725]  sda: sda1 sda2 sda3
[    3.303128] sd 2:0:0:0: [sda] Attached SCSI disk
your HDD appears OK. Thats it being discovered.

Code:
print_req_error: I/0 error, dev sda, sector #number
shows that there was a problem reading your HDD.
As that's a message from the kernel, it must have worked well enough for the kernel to be loaded.
That indicates that your motherboard is probably OK, as the motherboard is common to all disk IO.
The error is at the sector level. That's the kernel saying to the HDD give me sector X and the HDD responding I can't.

What happens next depends on what the data in the faulty sector was but it won't be good.

Long story short. You appear to have a hardware error.
Get smartmontools and post the output of
Code:
smartctl -a /dev/sda
if you can.

Do not attempt to write on what is probably a faulty drive.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Yamakuzure
Advocate
Advocate


Joined: 21 Jun 2006
Posts: 2273
Location: Bardowick, Germany

PostPosted: Wed Dec 05, 2018 12:42 pm    Post subject: Reply with quote

Another idea:
Is /dev/sda your SSD?
If it is, how full is it? Did you fstrim it since you got your laptop?
_________________
Important German:
  1. "Aha" - German reaction to pretend that you are really interested while giving no f*ck.
  2. "Tja" - German reaction to the apocalypse, nuclear war, an alien invasion or no bread in the house.
Back to top
View user's profile Send private message
denijane
n00b
n00b


Joined: 22 Jul 2014
Posts: 14

PostPosted: Thu Dec 06, 2018 12:18 am    Post subject: Reply with quote

Hi guys,
I'm sending my laptop to be repaired tomorrow, because today morning i found it unresponsive and i couldn't load the system anymore. Whatever the problem is, it escalated very quickly and killed it while i was backing up.

Yesterday I managed to run a smartmontools short test and it said the hard passed the test, but the first row (read_raw_something) said pre-failure state , all the other rows: "old age". It's my first ssd hard so i never knew i have to use fstrim or smartmontools. And I don't know if 7 months count as "old age" or there was something else.

So yeah, the hard is a toast. I'm thinking of switching to one M.2 SSD for the OS and regular SATA hard for everything else. It seems safer and easier to repair. But that's for when i can afford it.

Anyway, thank you all for trying to help me. At least I've learnt some things on how to check my SSD status, which will hopefully help me in the future to avoid such situations. Really, thanks a lot!
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43546
Location: 56N 3W

PostPosted: Thu Dec 06, 2018 6:25 pm    Post subject: Reply with quote

denijane,

You have just been unlucky.

smartmontools reads the drives internal error log' you don't need to run in as a matter of course but when all is not well, it can help determine if the problem is inside or outside the drive.
It works equally well on SSDs or rotating rust.

fstrim maintains the SSD write speed. The SSD write process can only change zeros into ones. That works provided that the area to be written has been erased' so that is is all zero.
Erase is a slow operation on SSDs so to maintain the write speed, needs a supply of erased blocks, ready to be written.
There are two ways to achieve that.

a) mount the filesystem with the discard option. This tells the kernel to send the trim command whenever it frees blocks on the SSD. The drive is than free to erase them whenever it wants to.
b) run fstrim in a cron job. This gives the drive a list of of all the unused blocks on the filesystem, including erased blocks. The drive works out what blocks need to be erased and adds them to its todo list.

Neither method is a command to the drive to perform any erases. Its up to the drive what it does and when. I'll gloss over why that is, its just a good thing for the drives life.
However, data recovery probably won't work after either of those options have been given.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7191
Location: Saint Amant, Acadiana

PostPosted: Thu Dec 06, 2018 6:42 pm    Post subject: Reply with quote

NeddySeagoon,

Code:
ata3: comreset failed error =-16


This is some sort of communication error, either the HDD control board or SATA controller is failing. Since this is a laptop there is no cable. However, re-seating the drive is something to try.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Unsupported Software All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum