Hi. There are two different system log messages that are bothering me:
This happens mostly when downloading at high speeds. My internet connection speed is 1Gb/s.
My connection is stable, and these messages are appearing without any disconnections.
What exactly does it mean and how to fix it ?
Second log messages are for one particular wifi device which is constantly connecting and disconnecting:
This is satellite decoder tv device (chip: Sagemcom Broadband SAS).
It is able to connet to both 2.4 GHZ and 5 GHZ, and signal / range is not an issue here.
Here are my wifi settings:
Anything that i can do or change to fix this issue ?
It happens regardless of the firmware that i am using (current one is 384.10_beta1)
Thanks in advance for any help !
Code:
Mar 18 11:29:41 kernel: blog_death_by_timeout: bad timeout value=18446744073709541616, extra_jiffies=30000, idle_jiffies=40000
Mar 18 11:29:54 kernel: blog_death_by_timeout: bad timeout value=18446744073709541616, extra_jiffies=30000, idle_jiffies=40000
Mar 18 11:29:55 kernel: blog_death_by_timeout: bad timeout value=18446744073709541616, extra_jiffies=30000, idle_jiffies=40000
Mar 18 11:30:12 kernel: blog_death_by_timeout: bad timeout value=18446744073709541616, extra_jiffies=30000, idle_jiffies=40000
Mar 18 11:30:13 kernel: blog_death_by_timeout: bad timeout value=18446744073709541616, extra_jiffies=30000, idle_jiffies=40000
This happens mostly when downloading at high speeds. My internet connection speed is 1Gb/s.
My connection is stable, and these messages are appearing without any disconnections.
What exactly does it mean and how to fix it ?
Second log messages are for one particular wifi device which is constantly connecting and disconnecting:
Code:
Mar 18 11:34:32 WLCEVENTD: Disassoc xx:xx:xx:xx:xx:xx
Mar 18 11:34:36 WLCEVENTD: Assoc xx:xx:xx:xx:xx:xx
This is satellite decoder tv device (chip: Sagemcom Broadband SAS).
It is able to connet to both 2.4 GHZ and 5 GHZ, and signal / range is not an issue here.
Here are my wifi settings:
Anything that i can do or change to fix this issue ?
It happens regardless of the firmware that i am using (current one is 384.10_beta1)
Thanks in advance for any help !