| jafa | I am running Ubuntu Server 24.04 on a set of machines with ASRock B640M motherboards (consumer-grade with Ryzen CPU)... when running and I press the power button Ubuntu Server shutsdown, the monitor turns off, but the motherboard+fans stay running | 01:09 |
|---|---|---|
| jafa | if I press F11 to get to the boot menu then press the power button the systems turn off | 01:10 |
| jafa | guessing it is the motherboard management microcontroller... does Ubuntu have any control over things? | 01:11 |
| sarnold | jafa: stick around for a bit, i've got ideas I've got to track down | 01:11 |
| jafa | what is further weird - motherboards purchased late last year (BIOS 1.18 upgraded to 3.08) shut down and turn off perfectly | 01:12 |
| jafa | motherboards purchased this year (same exact model and BIOS version 1.18) have the problem | 01:12 |
| jafa | systems are identical in hardware - same CPU, same GPU, same PSU | 01:15 |
| patdk-lap | could have been a motherboard schematic change | 01:16 |
| sarnold | oh that's weird .. maybe try to install firmware updates? if fwupd doesn't have them, check the asrock website? | 01:16 |
| jafa | I checked the markings on the motherboard - they have the same revision number | 01:16 |
| patdk-lap | heh, I stopped trusting revision numbers like 10years ago | 01:17 |
| jafa | :-) | 01:17 |
| patdk-lap | I forgot what it was, bought the same thing, same model number, got 5 different unmarked versions of it | 01:17 |
| jafa | when I upgrade from 1.18 to 3.01 it upgrades both the bios and the motherboard controller | 01:17 |
| trippeh | jafa: so 1.18 is probably the problem? | 01:17 |
| jafa | the 3 systems from last year shipped with 1.18, I upgraded 3.01, work fine | 01:18 |
| jafa | the next 6 systems built this year shipped with 1.18, I upgraded to 3.01, problem exists | 01:18 |
| jafa | built another system today and kept it on 1.18 to test - problem exists | 01:19 |
| sarnold | jafa: I'm guessing the kernel boot parameter "reboot" is the thing to tweak: https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/kernel-parameters.txt#L5616 | 01:19 |
| jafa | does that also apply to a shutdown? reboot works fine | 01:20 |
| sarnold | i'm not sure :/ | 01:20 |
| jafa | no harm in trying... brb... | 01:20 |
| === chris14_ is now known as chris14 | ||
| jafa | tried a few different reboot=xxx,xxx possibilities - no change | 01:54 |
| jafa | also pressing the power button when in this dead but on state doesn't turn the system off - requires a 5s press of the power button to turn the system off | 02:00 |
| oerheks | maybe you bios gives an option too, for pressing powerbutton. | 02:02 |
| oerheks | 10 seconds certainly shuts down hard. | 02:02 |
| sarnold | jafa: oh dang :( | 02:11 |
| jafa | I could maybe try installing a different OS on one system just to see if it will turn off... just can't quite bring myself to suffer through a different OS even if just a test :-) | 02:14 |
| jafa | Ubuntu 22.04 doesn't support this CPU or GPU | 02:15 |
| JanC | jafa: maybe go into the firmware setup and compare all options between the machines that work correctly & those that don't? | 02:44 |
| JanC | it might be something like wake-on-LAN or wake-on-USB or similar | 02:44 |
| jafa | hmmm... windows 10 setup can shutdown and turn off the system ok | 04:03 |
| jafa | installed to the point of creating an account, press the power button... shows a windows shutdown animated logo for a few seconds then the machine turns off | 04:03 |
| jafa | installed ubuntu server 24.04 and problem is back | 04:04 |
| jafa | bios settings are the same on all machines - reset to default, then a specific list of tweaks | 04:05 |
| jafa | oh! | 04:16 |
| jafa | JanC nailed it... I disabled the PCIe-wake feature and problem solved | 04:16 |
| jafa | I wonder which pcie device is holding wake | 04:17 |
| jafa | although somehow only affecting Ubuntu Server, not bios or windows-setup | 04:17 |
| jafa | could Ubuntu Server be enabling/configuring/triggering something on the PCIe bus causing a wake signal? | 05:14 |
| jafa | same problem with no PCIe cards installed so it has to be something built into the motherboard | 05:15 |
| jafa | I will try disabling the ethernet port in the bios | 05:15 |
| jafa | disabling onboard ethernet and audio doesn't avoid the problem | 05:33 |
| jafa | I will keep poking at it tomorrow | 05:46 |
| JanC | jafa: Windows might have one of those famous "motherboard driver" or "platform driver" things that only exist to work around hardware design bugs :) | 09:45 |
| JanC | or to work around ACPI bugs | 09:46 |
| === abydon2 is now known as abydon | ||
| ahasenack__ | any samba server admins here? I'm confused about samba-tool, is that meant to only be used locally, or can it also act on remote servers? | 15:14 |
| ahasenack__ | I would think that adding a user to a domain would just use my Administrator kerberos ticket and do it remotely, and in that way I could run it as a non-root user. But samba-tool is trying to write to /var/lib/samba/private/* | 15:15 |
| === ahasenack__ is now known as ahasenack | ||
| ahasenack | hm, -H perhaps | 15:18 |
| ahasenack | ok, this worked, but is more verbose than I expected | 15:19 |
| ahasenack | $ samba-tool user add ubuntu -H ldap://$(hostname -f) --use-kerberos=required | 15:19 |
| jafa | ran many more tests this morning - the only thing that works is disabling PCIe wakeup | 17:10 |
| jafa | I think we are good with doing that - these machines don't need wakeup | 17:11 |
| jafa | I have requested a bios update with that as the default from the motherboard vendor | 17:11 |
| muhopapa | hello | 17:50 |
| === BarnabasDK_ is now known as BarnabasDK | ||
| keithzg | Hmmmm I rebooted a 22.04 server to apply kernel updates and now none of the VirtualBox (6.1.50-dfsg-1~ubuntu1.22.04.1) machines it's set up to run are starting, all failing immediately with VERR_VMM_SET_JMP_ABORTED_RESUME | 23:39 |
| oerheks | dpkg-reconfigure virtualbox-dkms | 23:43 |
| oerheks | dpkg-reconfigure virtualbox | 23:43 |
| oerheks | modprobe vboxdrv' | 23:43 |
| oerheks | why not KVM? | 23:43 |
| keithzg | I wasn't even thinking about DKMS since it's always been such clearly kernel-module related errors before when that's been the problem, but that's a good idea | 23:44 |
| oerheks | have fun | 23:45 |
| keithzg | This was all set up for Windows VMs and generally for software testers to use fairly directly, so having the nice GUI interface with its various convenience features seemed necessary. Believe me I'd rather run KVM, hah! And for all the VMs that just run services or such that's exactly what I use. | 23:45 |
| keithzg | No dice with the dpkg-reconfigure, as expected but I did dare for a second to hope ;) | 23:48 |
| sarnold | does dmesg show any errors? journalctl for the virtualbox services? | 23:48 |
| patdk-lap | everyone is saying you need to upgrade to 7.0 | 23:51 |
| JanC | I think there are some fairly nice GUIs for libvirt/qemu/kvm also...? | 23:51 |
| patdk-lap | https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2073267 | 23:52 |
| -ubottu:#ubuntu-server- Launchpad bug 2073267 in virtualbox (Ubuntu) "Guru meditation on VM start" [Undecided, Confirmed] | 23:52 | |
| oerheks | maybe you run 7 already? | 23:52 |
| JanC | and if they lack some features you need, you should probably talk to their developers | 23:52 |
| oerheks | some bugs about that, ssh issues | 23:53 |
| oerheks | dispose old encryption, i say | 23:53 |
| sarnold | oww | 23:53 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!