On Mon, 2021-03-22 at 06:54 +0800, Ed Greshko wrote: > On 22/03/2021 06:36, Patrick O'Callaghan wrote: > > On Mon, 2021-03-22 at 06:12 +0800, Ed Greshko wrote: > > > On 22/03/2021 02:27, Chris Murphy wrote: > > > > Some folks are reporting a hang when booting Fedora 33 this > > > > morning > > > > (or also possibly wake from sleep). We're still digging into it > > > > but > > > > looks like a work around right now is to boot with parameter: > > > > systemd.mask=raid-check.timer > > > > > > > > You can subsequently 'systemctl disable raid-check.timer'. > > > > Folks > > > > with > > > > md raid setups might want to set a reminder to enable the timer > > > > again > > > > once the issue is sorted out. > > > > > > > It has been noted on the devel list that it only seems to fail if > > > the > > > time zone is set > > > to Europe/Dublin. > > > > > > Also, FWIW, when I used timedatectl to set my time zone to > > > Europe/Dublin my > > > system hung when doing an "init 6". > > Interesting. Does this happen with Europe/London (which is the > > exact > > same timezone)? > > I just tested and the answer is "no". > > Another interesting factoid. > > [egreshko@f33g ~]$ sudo timedatectl set-timezone Europe/Dublin > [egreshko@f33g ~]$ date > Sun Mar 21 22:49:06 GMT 2021 > [egreshko@f33g ~]$ sudo timedatectl set-timezone Asia/Taipei > > And the command is "hung" > > Until.... > > Failed to set time zone: Connection timed out Clearly BZ-worthy I'd say. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
