rogerjames99
Posts: 27
Joined: Fri Sep 28, 2012 2:58 pm

Spurious carriage return output to tty1 about 25/30 seconds after first login prompt following a boot

Tue Apr 16, 2019 6:17 pm

Has anyone else noticed this?

On a pi not running any graphical desktop. Boot or reboot and watch the boot log rolling up the screen. At the end of the boot sequence a login prompt appears on the first virtual console (tty1). Wait for about 30 seconds and a spurious carriage return is output to the console. This is really annoying if you happen to be typing in your user or password at the time.

Does anyone know where this is coming from? I have tried to track it down but with no luck.

It only appears on the first virtual console and only after a reboot, and only on recent rasbian versions.

Puzzled,

Roger

User avatar
FTrevorGowen
Forum Moderator
Forum Moderator
Posts: 4909
Joined: Mon Mar 04, 2013 6:12 pm
Location: Bristol, U.K.
Contact: Website

Re: Spurious carriage return output to tty1 about 25/30 seconds after first login prompt following a boot

Tue Apr 16, 2019 6:51 pm

rogerjames99 wrote:
Tue Apr 16, 2019 6:17 pm
Has anyone else noticed this?

On a pi not running any graphical desktop. Boot or reboot and watch the boot log rolling up the screen. At the end of the boot sequence a login prompt appears on the first virtual console (tty1). Wait for about 30 seconds and a spurious carriage return is output to the console. This is really annoying if you happen to be typing in your user or password at the time.

Does anyone know where this is coming from? I have tried to track it down but with no luck.

It only appears on the first virtual console and only after a reboot, and only on recent rasbian versions.

Puzzled,

Roger
IIRC, it's a known Debian issue (ie. "upstream" from Raspbian). Originally (again IIRC) keyboard entry was delayed &/or w/o cursor movement (there is an old thread quite a few months back). I share my USB keyboard & mouse with another computer via a USB switch so, by the time I've switched over "all is stable" and end up with some "over printing" of characters etc. Hopefully will be fully sorted when Raspbian Stretch becomes Raspbian Buster.
Trev.
Still running Raspbian Jessie on some older Pi's (an A, B1, B2, B+, P2B, 3xP0, P0W) but Stretch on my 2xP3A+, P3B+, P3B, B+, A+ and a B2. See: https://www.cpmspectrepi.uk/raspberry_pi/raspiidx.htm

rogerjames99
Posts: 27
Joined: Fri Sep 28, 2012 2:58 pm

Re: Spurious carriage return output to tty1 about 25/30 seconds after first login prompt following a boot

Wed Apr 17, 2019 9:11 am

Thanks Trevor

Do you have any more pointers that help be find the bug report over at Debian.

Roger

Ernst
Posts: 1092
Joined: Sat Feb 04, 2017 9:39 am
Location: Germany

Re: Spurious carriage return output to tty1 about 25/30 seconds after first login prompt following a boot

Wed Apr 17, 2019 11:50 am

rogerjames99 wrote:
Wed Apr 17, 2019 9:11 am
Thanks Trevor

Do you have any more pointers that help be find the bug report over at Debian.

Roger
A long time ago I did find something but now I can't find it at all. But somewhere in the back of my mind I seem to remember that it is related to fsck running in the background after reboot. While searching I found this https://gist.github.com/ebautistabar/82 ... d9048502b7. When I mask systemd-fsckd.service and systemd-fsckd.socket the problem did not appear. At the end of the post there is a link to https://salsa.debian.org/systemd-team/s ... 70313a8187 which might point to the culprit.
The road to insanity is paved with static ip addresses

User avatar
FTrevorGowen
Forum Moderator
Forum Moderator
Posts: 4909
Joined: Mon Mar 04, 2013 6:12 pm
Location: Bristol, U.K.
Contact: Website

Re: Spurious carriage return output to tty1 about 25/30 seconds after first login prompt following a boot

Wed Apr 17, 2019 4:30 pm

Ernst wrote:
Wed Apr 17, 2019 11:50 am
rogerjames99 wrote:
Wed Apr 17, 2019 9:11 am
Thanks Trevor

Do you have any more pointers that help be find the bug report over at Debian.

Roger
A long time ago I did find something but now I can't find it at all. But somewhere in the back of my mind I seem to remember that it is related to fsck running in the background after reboot. While searching I found this https://gist.github.com/ebautistabar/82 ... d9048502b7. When I mask systemd-fsckd.service and systemd-fsckd.socket the problem did not appear. At the end of the post there is a link to https://salsa.debian.org/systemd-team/s ... 70313a8187 which might point to the culprit.
Thanks @Ernst for that - I also vaguely recalled that there was a "workaround/crude fix" mentioned in a thread here or elsewhere but hadn't followed through to that in "any detail".
Trev.
Still running Raspbian Jessie on some older Pi's (an A, B1, B2, B+, P2B, 3xP0, P0W) but Stretch on my 2xP3A+, P3B+, P3B, B+, A+ and a B2. See: https://www.cpmspectrepi.uk/raspberry_pi/raspiidx.htm

Return to “Raspbian”