On 3/15/21 9:38 AM, John Paul Adrian Glaubitz wrote:
> Hello!
>
> On 3/15/21 10:34 AM, Anatoly Pugachev wrote:
>>> + /usr/sbin/grub-probe --target=device /
>>> + GRUB_DEVICE=/dev/sda2
>>> + /usr/sbin/grub-probe --device /dev/sda2 --target=fs_uuid
>>> [ 1330.951329] watchdog: BUG: soft lockup - CPU
Hello!
On 3/15/21 10:34 AM, Anatoly Pugachev wrote:
>> + /usr/sbin/grub-probe --target=device /
>> + GRUB_DEVICE=/dev/sda2
>> + /usr/sbin/grub-probe --device /dev/sda2 --target=fs_uuid
>> [ 1330.951329] watchdog: BUG: soft lockup - CPU#0 stuck for 22s!
>> [grub-probe:443]
>> [ 1331.046350] Modules
On Mon, Mar 15, 2021 at 4:59 AM Dennis Clarke wrote:
>
>
> While digging around here I saw that update-grub will lead to a lockup
> every time. So I simply changed /usr/sbin/grub-mkconfig script to
> allow me to see everything that happens.
>
> That gets me to :
>
> /usr/sbin/grub-probe --d
While digging around here I saw that update-grub will lead to a lockup
every time. So I simply changed /usr/sbin/grub-mkconfig script to
allow me to see everything that happens.
That gets me to :
/usr/sbin/grub-probe --device /dev/sda2 --target=fs_uuid
which falls to pieces perfectly :
4 matches
Mail list logo