Github messages for voidlinux
 help / color / mirror / Atom feed
From: foopub <foopub@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Dracut message on system boot
Date: Wed, 03 Feb 2021 17:58:04 +0100	[thread overview]
Message-ID: <20210203165804.ljx-Mwa9t00wmbjHBLpNmQV9JjQErp8sOm-nRqoLs_Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13024@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]

New comment by foopub on void-packages repository

https://github.com/void-linux/void-packages/issues/13024#issuecomment-772661674

Comment:
> Herewith, a couple of observations:
> 
>     * The write error is not from `stat`, `tr` or anything like that. It's the kernel rejecting the values you're trying to write to `/sys/power/resume`.
> 
>     * The output of the `ls` scrape is _not_ the same as that from `stat`. `ls` prints device types in decimal, but `stat` prints hex values:
> 
> 
> ```
> % ls -lH /dev/watchdog
> crw------- 1 root root 10, 130 Jan 25 23:43 /dev/watchdog
> 
> % stat /dev/watchdog -c '%t:%T'
> a:82
> ```
> 
>     * Sometimes these sysfs writes are finicky, and a terminating newline can cause a problem. In the original `ls` scrape, you can try `echo -n` to suppress the new line. In the `stat` version, you can use `tr -d '\n'`.

Aight, good points! It seems the kernel won't accept wrong values in the correct format either. Running `stat $resume -c %t:%T | tr -d '\n'` inside the script actually prints 0:0 (instead of 8:3 which is my swap file) and is also rejected.

Perhaps the stem of the issue is $resume pointing to the wrong thing?

  parent reply	other threads:[~2021-02-03 16:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12  8:00 [ISSUE] " voidlinux-github
2019-07-25 16:14 ` voidlinux-github
2019-07-25 16:49 ` voidlinux-github
2019-07-25 17:04 ` voidlinux-github
2019-07-25 17:19 ` voidlinux-github
2019-07-25 17:34 ` voidlinux-github
2019-07-25 17:51 ` voidlinux-github
2019-07-25 17:54 ` voidlinux-github
2019-07-25 18:25 ` voidlinux-github
2019-07-26 20:59 ` voidlinux-github
2019-07-26 21:22 ` voidlinux-github
2021-02-03 15:16 ` foopub
2021-02-03 15:50 ` foopub
2021-02-03 16:11 ` ahesford
2021-02-03 16:58 ` foopub [this message]
2021-02-03 17:06 ` foopub
2021-02-03 17:22 ` foopub
2022-04-15  2:12 ` github-actions
2022-04-29  2:13 ` [ISSUE] [CLOSED] " github-actions

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210203165804.ljx-Mwa9t00wmbjHBLpNmQV9JjQErp8sOm-nRqoLs_Q@z \
    --to=foopub@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).