kjac Posted October 30, 2020 Share Posted October 30, 2020 I'm in the process of running memtest to rule out the ram as the logs don't really show any obvious errors that I can see. The only ones that stand out are: Oct 29 06:26:43 Tower kernel: br0: received packet on bond0 with own address as source address (addr:xx:xx:xx:xx:xx:xx, vlan:0) which is also the last entry in the log file before crashing. I uploaded the diagnostics archive, however the log file inside wasn't the full syslog server logs so I uploaded that separate as "syslog-full.txt" I also took a picture of my monitor as it looked after a crash, it was stuck on this screen. Most of the time after it crashes it just gets stuck on the usb OS boot selection screen, however. tower-diagnostics-20201029-1954.zip syslog-full.txt Quote Link to comment
kjac Posted October 30, 2020 Author Share Posted October 30, 2020 36 minutes ago, trurl said: Thanks. I changed the PSIC setting in bios to "typical current idle" as suggested in that thread. I'll see if that improves things. Would this potentially correct the "br0: received packet on bond0 with own address as source address" error that I keep getting? I keep seeing something about needing to enable bonding on my router or something, however I'm not sure that's the answer for my setup. I've got a netgear r7000 router connected to an 8 port unmanaged switch that feeds all my wired devices. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.