sage2050
-
Posts
92 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by sage2050
-
-
I did some more messing around and after another short period of instability I feel fairly confident that my crashes were related to binding the two unused USB controllers that are included with my GPU. In my VM settings i set PCIe ACS override to "both" and was able to bind only the video and audio devices on the GPU for passthrough and I haven't seen any call traces in 10 days now.
During my previous stable period I wasn't binding any IOMMU groups.
-
I;ve had to delete and rebuild my docker img many times using this build. the first time was because it filled up, so i increased the size to 30gb (using a container that needs a heap of its own space), but even after that and deleting that particular container my img seems to be corrupting like once a week. I can't start, stop, or use certain containers (never the same one) and when I stop the docker service it refuses to restart with the error below and then I have to rebuild.
-
15 days of uptime. going on a trip for 4 days, I got a feeling it's going to go down as soon as I walk out the door.
-
hmm
Apr 1 18:40:17 Servbot kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Down Apr 1 18:40:17 Servbot kernel: bond0: (slave eth0): link status definitely down, disabling slave Apr 1 18:40:17 Servbot kernel: device eth0 left promiscuous mode Apr 1 18:40:17 Servbot kernel: bond0: now running without any active interface! Apr 1 18:40:17 Servbot kernel: br0: port 1(bond0) entered disabled state Apr 1 18:40:20 Servbot kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Apr 1 18:40:20 Servbot kernel: bond0: (slave eth0): link status definitely up, 1000 Mbps full duplex Apr 1 18:40:20 Servbot kernel: bond0: (slave eth0): making interface the new active one Apr 1 18:40:20 Servbot kernel: device eth0 entered promiscuous mode Apr 1 18:40:20 Servbot kernel: bond0: active interface up! Apr 1 18:40:20 Servbot kernel: br0: port 1(bond0) entered blocking state Apr 1 18:40:20 Servbot kernel: br0: port 1(bond0) entered forwarding state
-
*sigh* got a call trace this morning, but the server recovered at least. I hadn't even started activating dockers yet.
I haven't seen any network issues in the log but i'll keep an eye out.
edit: this trace was related to a scheduled ca backup/restore which is currently incompatible wtih 6.12 and i hadn't disabled it. I'll chalk it up to that.
-
Knocking on every piece of wood and tree in sight, but I crossed over 1 week of uptime last night after changing docker from macvlan to iplan. I also disabled some less than crucial dockers so I'll start enabling them one by one.
-
glad I found this thread, been dealing with kernel panics for the last month or so and can't for the life of me find the solution. It started after i installed a gpu and setup a vm to pass it to - never had any issues before, and disabling the vm doesn't stop the kernel panics. I upgraded from 6.11 to 6.12.0-rc2 and having the same problems. Going to dig through this thread a bit.
6.9.0/6.9.1 - Kernel Panic due to netfilter (nf_nat_setup_info) - Docker Static IP (macvlan)
in Stable Releases
Posted
do you have an external gpu installed?