Search Linux Wireless

Re: rtw88: 8822cu (LM842) --> LOWER_UP link messages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Actually the connection is not dropped. That is the problem : the
message LOWER_UP is coming although the connection is not dropped.

I suppose that LOWER_UP notification is send wrong by the driver.

In the log nothing comes.
I tried to increase log level, but I didn't find any /proc/rtw88.
I have debug activated:
CONFIG_RTW88_DEBUG=y
CONFIG_RTW88_DEBUGFS=y

On Fri, Apr 28, 2023 at 9:28 PM Larry Finger <Larry.Finger@xxxxxxxxxxxx> wrote:
>
> On 4/28/23 08:56, Gabriel Tisan wrote:
> > Hi !
> >
> > I use a LM842 wifi stick on a Linux kernel 5.15 with last patches for
> > rtw88 from linux-next applied.
> > Firmware version is 9.9.15
> >
> > When I connect LM842 as a station to an AP, after the link is up first
> > time, it comes from time to time more LOWER_UP message.
> > The stick is plugged and the connection to AP is still valid.
> >
> > # ip -oneline -family inet monitor link
> >
> > 5: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN
> > group default \    link/ether 34:c9:f0:99:b6:a1 brd ff:ff:ff:ff:ff:ff
> >
> > 5: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
> > state DOWN group default \    link/ether 34:c9:f0:99:b6:a1 brd
> > ff:ff:ff:ff:ff:ff
> >
> > 5: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
> > state DOWN group default \    link/ether 34:c9:f0:99:b6:a1 brd
> > ff:ff:ff:ff:ff:ff
> >
> > 5: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> \    link/ether
> >
> > 5: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
> > noqueue state DORMANT group default \    link/ether 34:c9:f0:99:b6:a1
> > brd ff:ff:ff:ff:ff:ff
> >
> > 5: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> \    link/ether
> >
> > 5: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> \    link/ether
> >
> > 5: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> \    link/ether
> >
> > 5: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
> > state UP group default \    link/ether 34:c9:f0:99:b6:a1 brd
> > ff:ff:ff:ff:ff:ff
> >
> >
> >
> > 5: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> \    link/ether
> >
> > 5: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> \    link/ether
> >
> > 5: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> \    link/ether
> >
> > 5: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> \    link/ether
> >
> > 5: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> \    link/ether
> >
> > 5: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> \    link/ether
> >
> >
> >
> >
> >
> > Any idea what I can do ?
> >
> > Did someone also reproduce that problem ?
>
> No, I do not see that problem. When I run your command, I get
>
> finger@localhost:~/rtw88>ip -oneline -family inet monitor link
> 12: wlp0s20u6i2: <BROADCAST,MULTICAST,UP,LOWER_UP> \    link/ether
> 12: wlp0s20u6i2: <BROADCAST,MULTICAST,UP,LOWER_UP> \    link/ether
> 12: wlp0s20u6i2: <BROADCAST,MULTICAST,UP,LOWER_UP> \    link/ether
>
> My connection is very stable; however, my device is an 8822BU, not an 8822CU.
>
> When the connection is dropped, what is logged? You can see that with a 'sudo
> dmesg | less' command.
>
> Larry
>
>




[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Wireless Regulations]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux