Your message dated Mon, 27 Mar 2017 14:50:11 +0100 with message-id <1490622611.2634.9.camel@decadent.org.uk> and subject line Re: Bug#858824: Disrupting messages to tty has caused the Debian Bug report #858824, regarding Disrupting messages to tty to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 858824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858824 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Disrupting messages to tty
- From: Leon Meier <Leon.Meier@yandex.ru>
- Date: Mon, 27 Mar 2017 12:11:26 +0200
- Message-id: <[🔎] d5a46d73-6483-5222-3eb1-a601b3035ae5@yandex.ru>
Package: firmware-iwlwifi Version: 20161130-2When I'm doing whatever tasks in tty..., following messages get printed to the screen every couple of minutes:iwlwifi ... L1 Enabled - LTR Disabled along with a bunch of other, mostly iwlwifi-related messages.They disrupt my workflow, overwriting the current screen contents. This is annoying. Are these messages important? Could these messages better go somewhere else?Thanks is advance Leon[ 1917.007948] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 1917.014919] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 1917.015108] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1 [ 1917.244098] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 1917.251786] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 1917.251981] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1 [ 1917.349565] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2233.012506] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 2233.032397] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 2233.032593] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1 [ 2233.273367] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 2233.280979] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 2233.281169] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1 [ 2233.394848] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2280.802538] perf: interrupt took too long (3934 > 3917), lowering kernel.perf_event_max_sample_rate to 50750 [ 2549.008539] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 2549.015471] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 2549.015660] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1 [ 2549.251304] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 2549.258240] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 2549.258433] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1 [ 2549.354601] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2864.995743] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 2865.002684] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 2865.002879] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1 [ 2865.270886] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 2865.277820] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 2865.278009] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1 [ 2865.381159] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 3180.998535] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 3181.005556] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 3181.005743] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1 [ 3181.237671] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 3181.244599] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled [ 3181.244788] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1 [ 3181.343180] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 3358.835933] perf: interrupt took too long (4932 > 4917), lowering kernel.perf_event_max_sample_rate to 40500
--- End Message ---
--- Begin Message ---
- To: 858824-done@bugs.debian.org
- Subject: Re: Bug#858824: Disrupting messages to tty
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Mon, 27 Mar 2017 14:50:11 +0100
- Message-id: <1490622611.2634.9.camel@decadent.org.uk>
- In-reply-to: <[🔎] d5a46d73-6483-5222-3eb1-a601b3035ae5@yandex.ru>
- References: <[🔎] d5a46d73-6483-5222-3eb1-a601b3035ae5@yandex.ru>
This is not a bug. Use a support channel to ask questions about managing console output: https://www.debian.org/support Ben. -- Ben Hutchings Always try to do things in chronological order; it's less confusing that way.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---