[opensuse-factory] /etc/issue banner repeating on serial
Hi, For some months, Tumbleweed displays IP addresses on the serial console, as in:
Welcome to openSUSE Tumbleweed 20170617 - Kernel 4.12.0-rc5-1.g270295f-lpae (ttyAMA0).
eth0: <IPv4> <IPv6>
raspi2 login: Welcome to openSUSE Tumbleweed 20170617 - Kernel 4.12.0-rc5-1.g270295f-lpae (ttyAMA0).
eth0: <IPv4> <IPv6>
raspi2 login: [...]
Annoyingly this output keeps repeating every few minutes, so that useful kernel output may scroll out of screen over time. Previously, the static banner was displayed only once, and pressing ENTER was an easy enough way to get a new login prompt with banner. By my reading of /usr/lib/udev/rules.d/90-issue-generator.rules, issue-generator should only be called when net devices are added/removed, which does not seem to be happening in my case (judging by /run/issue timestamp). Why is /etc/issue printed more than once? The IP addresses don't change. Thanks for any hints, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Andreas Färber
Hi,
For some months, Tumbleweed displays IP addresses on the serial console, as in:
Welcome to openSUSE Tumbleweed 20170617 - Kernel 4.12.0-rc5-1.g270295f-lpae (ttyAMA0).
eth0: <IPv4> <IPv6>
raspi2 login: Welcome to openSUSE Tumbleweed 20170617 - Kernel 4.12.0-rc5-1.g270295f-lpae (ttyAMA0).
eth0: <IPv4> <IPv6>
raspi2 login: [...]
Annoyingly this output keeps repeating every few minutes, so that useful kernel output may scroll out of screen over time.
I don't see that and have Tw current. I see the openSUSE greeting and version identification and network connection, but only once. and this is a new install, second day.
Previously, the static banner was displayed only once, and pressing ENTER was an easy enough way to get a new login prompt with banner.
By my reading of /usr/lib/udev/rules.d/90-issue-generator.rules, issue-generator should only be called when net devices are added/removed, which does not seem to be happening in my case (judging by /run/issue timestamp).
Why is /etc/issue printed more than once? The IP addresses don't change.
I don't see it on my five boxes. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 18.06.2017 um 17:42 schrieb Patrick Shanahan:
* Andreas Färber
[06-18-17 10:42]: For some months, Tumbleweed displays IP addresses on the serial console, as in:
Welcome to openSUSE Tumbleweed 20170617 - Kernel 4.12.0-rc5-1.g270295f-lpae (ttyAMA0).
eth0: <IPv4> <IPv6>
raspi2 login: Welcome to openSUSE Tumbleweed 20170617 - Kernel 4.12.0-rc5-1.g270295f-lpae (ttyAMA0).
eth0: <IPv4> <IPv6>
raspi2 login: [...]
Annoyingly this output keeps repeating every few minutes, so that useful kernel output may scroll out of screen over time.
I don't see that and have Tw current. I see the openSUSE greeting and version identification and network connection, but only once. and this is a new install, second day.
Previously, the static banner was displayed only once, and pressing ENTER was an easy enough way to get a new login prompt with banner.
By my reading of /usr/lib/udev/rules.d/90-issue-generator.rules, issue-generator should only be called when net devices are added/removed, which does not seem to be happening in my case (judging by /run/issue timestamp).
Why is /etc/issue printed more than once? The IP addresses don't change.
I don't see it on my five boxes.
Thanks for that input, Patrick. I see it on pretty much all of my ARM boxes (more than five). Most of these are zypper dup'ed system, but I've also seen it with recent JeOS images. Since you're not seeing the same, I've filed it as a bug: https://bugzilla.opensuse.org/show_bug.cgi?id=1044819 Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
18.06.2017 17:42, Andreas Färber пишет:
Why is /etc/issue printed more than once? The IP addresses don't change.
Well, the problem is obviously not IP address change, but the fact that (a)getty gets reinitialized and redisplays /etc/issue. This could be result of - (some) interfaces constantly appear and disappear. They do not need to be the same which IPs are displayed - every time interface is added or deleted (i.e. kernel event happens), issue-generator runs "agetty --reload". In principle, buggy driver sending periodic add events cannot be excluded either. - getty service gets restarted for some reasons - something keeps changing /run/agetty.reload time-stamp - etc ... So you really need to debug it on your system. The fact that it started to happen when issue-generator was introduced does not mean it is caused by issue generator. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, Jun 18, Andrei Borzenkov wrote:
18.06.2017 17:42, Andreas Färber пишет:
Why is /etc/issue printed more than once? The IP addresses don't change.
Well, the problem is obviously not IP address change, but the fact that (a)getty gets reinitialized and redisplays /etc/issue. This could be result of
- (some) interfaces constantly appear and disappear. They do not need to be the same which IPs are displayed - every time interface is added or deleted (i.e. kernel event happens), issue-generator runs "agetty --reload". In principle, buggy driver sending periodic add events cannot be excluded either.
"agetty --reloaded" is only called if an interface in /etc/issue is added or removed, not for every random network interface.
So you really need to debug it on your system. The fact that it started to happen when issue-generator was introduced does not mean it is caused by issue generator.
Easy to find out: edit /etc/sysconfig/issue-generator and disable the network interfaces. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 06/18/2017, 10:01 PM, Thorsten Kukuk wrote:
So you really need to debug it on your system. The fact that it started to happen when issue-generator was introduced does not mean it is caused by issue generator.
Easy to find out: edit /etc/sysconfig/issue-generator and disable the network interfaces.
Making it: NETWORK_INTERFACE_REGEX="^xxx[be]" no longer causes the repeats. It seems to update with every ipv6 RA here. regards, -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, Jun 20, 2017 at 4:28 PM, Jiri Slaby
On 06/18/2017, 10:01 PM, Thorsten Kukuk wrote:
So you really need to debug it on your system. The fact that it started to happen when issue-generator was introduced does not mean it is caused by issue generator.
Easy to find out: edit /etc/sysconfig/issue-generator and disable the network interfaces.
Making it: NETWORK_INTERFACE_REGEX="^xxx[be]" no longer causes the repeats.
It seems to update with every ipv6 RA here.
Could you capture "udevadm monitor --property" output for these events? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 06/20/2017, 03:37 PM, Andrei Borzenkov wrote:
On Tue, Jun 20, 2017 at 4:28 PM, Jiri Slaby
wrote: On 06/18/2017, 10:01 PM, Thorsten Kukuk wrote:
So you really need to debug it on your system. The fact that it started to happen when issue-generator was introduced does not mean it is caused by issue generator.
Easy to find out: edit /etc/sysconfig/issue-generator and disable the network interfaces.
Making it: NETWORK_INTERFACE_REGEX="^xxx[be]" no longer causes the repeats.
It seems to update with every ipv6 RA here.
Could you capture "udevadm monitor --property" output for these events?
There are none = no output :). -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Andreas Färber
-
Andrei Borzenkov
-
Jiri Slaby
-
Patrick Shanahan
-
Thorsten Kukuk