|
The_Franz posted:that's generally how logs look when hardware is going bad yes, that and the same thing happening on two unrelated os installs would definitely be an indicator that poo poo be hosed. otoh, maybe OP can just keep installing distros until they find one that doesn't care about failing hardware
|
# ? Jan 31, 2021 16:04 |
|
|
# ? May 28, 2024 18:21 |
|
Nitrousoxide posted:Wow! Impressive! Fedora is so advanced it is planning future kernel core dumps. "signalize"?
|
# ? Jan 31, 2021 16:54 |
|
nice thread title
|
# ? Jan 31, 2021 17:05 |
|
Lysidas posted:"signalize"?
|
# ? Jan 31, 2021 17:50 |
|
Lysidas posted:"signalize"? signalize, it's a word, look it up https://www.youtube.com/watch?v=wpEaFmK3lrY
|
# ? Jan 31, 2021 17:54 |
|
infernal machines posted:yes, that and the same thing happening on two unrelated os installs would definitely be an indicator that poo poo be hosed. Its what I do I still believe that gentoo will last the longest because it compiles around the hardware problem. Like a learning machine, it simply finds new ways to make things work
|
# ? Jan 31, 2021 17:55 |
|
maybe it's a noisy kernel and not hardware errors unless we can see the actual logs that cause the report to be made in the first place then we just don't know Is your process table just chock full of the same kernel process? If a kernel process actually crashed, then the kernel won't be able to clean it up and will just leave it there. On the other hand, it could just be a helper process in userspace although that should probably yield the frames to get a report generated.
|
# ? Jan 31, 2021 18:19 |
|
isn’t it the other way around? like a competent distro will ship a kernel with symbols enabled so you can always get a usable backtrace from an oops, but you need debuginfo installed to get a good backtrace in userspace
|
# ? Jan 31, 2021 18:32 |
infernal machines posted:have you run memtest? you know, just for the hell of it? Yep! No memory errors on a full 4ish hour memtest. I'm also running a S.M.A.R.T. diagnostic just in case the drive is going bad and a bunch of bad data got written/corrupted in the install, but I doubt that is it since the windows install on that same drive is fine. I assume the future kernel error is just it reporting the error in UTC time before it was connected to the internet to sync up the system clock, and thus reporting it 5 hours ahead of local. I do have some weird hardware issues going on though. My ethernet device was failing to grab an IP address under DHCP on three different OS's, Fedora, PopOS and even Windows. It took booting into Windows and, because I'm familiar with how to do it there, forcing a reset of the device, to fix it across all OS's, at least for the time. I'm probably going with what I've read online about my motherboard from people who have this one and have tried to use it with Linux. That it just plays really wacky with Unix-like systems.
|
|
# ? Jan 31, 2021 20:18 |
|
Nitrousoxide posted:I'm probably going with what I've read online about my motherboard from people who have this one and have tried to use it with Linux. That it just plays really wacky with Unix-like systems.
|
# ? Jan 31, 2021 21:14 |
Bourricot posted:If I read your inxi log properly, your mobo is still using the f2 bios (released in April 2017). According to Gigabyte's website, there's a bunch of bios updates available. It might be worth updating and see if that fixes your issues. I actually went an applied those yesterday (after I took the inxi report) for this exact reason. No improvement in the issues, though the computer does boot faster now.
|
|
# ? Jan 31, 2021 21:23 |
|
Then it might be time to fiddle with the bios settings. I know that with my B450 mobo, I had to disable "CPU Performance Boost" to get rid of some stability issues with Linux. Not saying it might be the same for you, but looking around the various CPU options in the bios may help.
|
# ? Jan 31, 2021 21:34 |
|
AnimeIsTrash posted:Same, the only time Arch has completely wrecked my system was in college when they made the transition from init to systemd. There was this very convoluted system for how to transition if you didn't want to wipe and reinstall the OS and it completely hosed my computer. my hosed arch story is me starting a system update and then a few minutes later forgetting that i had done so as i unplugged the computer to move it. iirc it resulted in some critical libraries being missing and i couldn't be bothered to boot off usb or whatever to fix it its on me for unplugging it to begin with but also on arch that their packaging can apparently leave things in a limbo state at some point in the update process
|
# ? Jan 31, 2021 21:36 |
|
Progressive JPEG posted:my hosed arch story is me starting a system update and then a few minutes later forgetting that i had done so as i unplugged the computer to move it. iirc it resulted in some critical libraries being missing and i couldn't be bothered to boot off usb or whatever to fix it Yes I also regularly unplug computers mid-update then blame issues on the package manager.
|
# ? Jan 31, 2021 21:45 |
|
yeah, what? a package manager is supposed to expect random power outages during installs? even if it did, turning off. a machine during writes will gently caress something up
|
# ? Jan 31, 2021 21:55 |
|
spankmeister posted:Yes I also regularly unplug computers mid-update then blame issues on the package manager. i had the power cut during an update last year it's fedora which does offline updates though, so it was fine
|
# ? Jan 31, 2021 22:19 |
|
i think the guy huffing laughing gas running arch for gamers, their grey forums question, the cause is probably their gigabyte motherboard. in my experience their gear is no bueno and their support is industry leading, if the goal is to provide the worst support possible. i have never had any issues with arch, though i don't use it (or linux) that often. if i'm linuxing at home though, it's probably arch because it's easy to reconfigure to what i want
|
# ? Jan 31, 2021 23:04 |
|
|
# ? Jan 31, 2021 23:15 |
|
Nomnom Cookie posted:isn’t it the other way around? like a competent distro will ship a kernel with symbols enabled so you can always get a usable backtrace from an oops, but you need debuginfo installed to get a good backtrace in userspace I agree that an actual oops usually gives a pretty reasonable traceback. I don't know if this error reporting package is actually smart enough to root through dmesg to pull out the backtrace, or if some other issue is happening that causes the package to consider the event to be an error. We just don't know until we have the log that is actually triggering the reporting system. Nitrousoxide, does the dmesg tool show anything useful?
|
# ? Jan 31, 2021 23:39 |
|
hahahhahaha
|
# ? Jan 31, 2021 23:45 |
|
Bourricot posted:Then it might be time to fiddle with the bios settings. because the pc components market mostly produces trash for gamerbros, lots of motherboards have default settings which overclock the cpu and/or ram. makes their board look better in lazy reviews which don't try to correct for fuckery like that, often causes instability.
|
# ? Jan 31, 2021 23:55 |
sb hermit posted:I agree that an actual oops usually gives a pretty reasonable traceback. Here's the dmesg for a couple of the events. https://pastebin.com/pLb5Yauh https://pastebin.com/QK1a7CWD Personally it looks like a motherboard issue from the end of the log. Oddly enough I haven't gotten any today? This is a really weird problem I'm having across distros. It's gotta be a hardware problem, and memtest/SMART both confirm no failure on the part of RAM and storage, which would be where I expect to see this stuff popping up. I suppose theoretically it could be the CPU (though if it's throwing out garbage calculations I would expect that to show up in the memtest) Nitrousoxide fucked around with this message at 02:00 on Feb 1, 2021 |
|
# ? Feb 1, 2021 01:57 |
|
Nitrousoxide posted:Here's the dmesg for a couple of the events. Looks like you need to play around with your ethernet card, eno1 quote:[ 9.653914] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready Likely, you will need new or better firmware.
|
# ? Feb 1, 2021 02:50 |
|
A netdev timeout is only bad if you want good performance out of your network card. Otherwise, you can disable it in the bios and those errors should go away.
|
# ? Feb 1, 2021 02:53 |
|
quote:[ 5.154831] cfg80211: Loading compiled-in X.509 certificates for regulatory database well, wifi might not work either
|
# ? Feb 1, 2021 03:00 |
|
Nitrousoxide posted:Wow! Impressive! Fedora is so advanced it is planning future kernel core dumps.
|
# ? Feb 1, 2021 03:06 |
decided to try livebooting fedora from a USB on my laptop to see how it'd go. the ASUS ZenBook's touchpad is actually asecond screen for some stupid loving reason and, well... and yes i had to navigate to the display settings from the touchpad to fix it
|
|
# ? Feb 1, 2021 21:25 |
|
2021 is the Year of Linux on the Trackpad
|
# ? Feb 1, 2021 21:31 |
|
i vomit kittens posted:decided to try livebooting fedora from a USB on my laptop to see how it'd go. the ASUS ZenBook's touchpad is actually asecond screen for some stupid loving reason and, well... it truly is the year of linux on the desktop
|
# ? Feb 1, 2021 21:31 |
|
i vomit kittens posted:decided to try livebooting fedora from a USB on my laptop to see how it'd go. the ASUS ZenBook's touchpad is actually asecond screen for some stupid loving reason and, well... lol if they did this to one-up apple touchbar and the rumors of apple shitcanning the touchbar turn out to be true
|
# ? Feb 1, 2021 21:48 |
|
BobHoward posted:lol if they did this to one-up apple touchbar and the rumors of apple shitcanning the touchbar turn out to be true that's actually the sane way they did it because it doesn't mess with ergonomics like their gigantic touchbar does
|
# ? Feb 1, 2021 21:54 |
|
i vomit kittens posted:decided to try livebooting fedora from a USB on my laptop to see how it'd go. the ASUS ZenBook's touchpad is actually asecond screen for some stupid loving reason and, well... lmao
|
# ? Feb 1, 2021 21:55 |
|
i vomit kittens posted:decided to try livebooting fedora from a USB on my laptop to see how it'd go. the ASUS ZenBook's touchpad is actually asecond screen for some stupid loving reason and, well... ahhhh yeah this is the sort of poo poo I come to the linux thread for
|
# ? Feb 1, 2021 22:11 |
|
i vomit kittens posted:decided to try livebooting fedora from a USB on my laptop to see how it'd go. the ASUS ZenBook's touchpad is actually asecond screen for some stupid loving reason and, well... goddamn
|
# ? Feb 1, 2021 22:13 |
|
i vomit kittens posted:decided to try livebooting fedora from a USB on my laptop to see how it'd go. the ASUS ZenBook's touchpad is actually asecond screen for some stupid loving reason and, well... lmao
|
# ? Feb 1, 2021 22:23 |
|
i vomit kittens posted:decided to try livebooting fedora from a USB on my laptop to see how it'd go. the ASUS ZenBook's touchpad is actually asecond screen for some stupid loving reason and, well... expected linux behavior
|
# ? Feb 1, 2021 22:26 |
|
tbh i'm not even sure it's a linux thing, obvs the display is just a mini touch screen connected to a regular gpu video out and asus set up the bios so it can be detected as if it's the main display and never bothered to test w/ linux it's still really funy tho lmao
|
# ? Feb 1, 2021 22:31 |
|
i vomit kittens posted:decided to try livebooting fedora from a USB on my laptop to see how it'd go. the ASUS ZenBook's touchpad is actually asecond screen for some stupid loving reason and, well... Lmfao
|
# ? Feb 1, 2021 22:48 |
|
i vomit kittens posted:decided to try livebooting fedora from a USB on my laptop to see how it'd go. the ASUS ZenBook's touchpad is actually asecond screen for some stupid loving reason and, well... lol
|
# ? Feb 1, 2021 22:49 |
|
|
# ? May 28, 2024 18:21 |
|
i vomit kittens posted:decided to try livebooting fedora from a USB on my laptop to see how it'd go. the ASUS ZenBook's touchpad is actually asecond screen for some stupid loving reason and, well...
|
# ? Feb 1, 2021 22:51 |