mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: enc0der <enc0der@gmail.com>
Cc: "Linux Regressions" <regressions@lists.linux.dev>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Wireless" <linux-wireless@vger.kernel.org>,
	"Linux Networking" <netdev@vger.kernel.org>,
	"Linux USB" <linux-usb@vger.kernel.org>,
	"Linux RCU" <rcu@vger.kernel.org>,
	"Stanislaw Gruszka" <stf_xl@wp.pl>,
	"Helmut Schaa" <helmut.schaa@googlemail.com>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Hayes Wang" <hayeswang@realtek.com>,
	"Simon Horman" <horms@kernel.org>,
	"Andre Przywara" <andre.przywara@arm.com>,
	"Andrew Gaul" <gaul@gaul.org>, "Bjørn Mork" <bjorn@mork.no>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	"Frederic Weisbecker" <frederic@kernel.org>,
	"Neeraj Upadhyay" <quic_neeraju@quicinc.com>,
	"Joel Fernandes" <joel@joelfernandes.org>,
	"Josh Triplett" <josh@joshtriplett.org>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
	"Lai Jiangshan" <jiangshanlai@gmail.com>,
	Zqiang <qiang.zhang1211@gmail.com>
Subject: Re: rt8000usb driver issue (maybe interaction with other drivers)
Date: Sun, 1 Oct 2023 12:53:22 +0700	[thread overview]
Message-ID: <3d246a72-2755-484f-8274-0c61fc185592@gmail.com> (raw)
In-Reply-To: <CAEXpi5RiLbma5cb-ctEvvb7LGRn78VTOh5HDmreC2hYgtBEQog@mail.gmail.com>

On 01/10/2023 12:33, enc0der wrote:
> Hello Bagas,
> 
> The distro I am using is:
> Jetson Linux 35.4.1 which is is part of JetPack 5.1.2
> 
> Supported Linux Kernel version: 5.10 LTS
> aarch64
> sample root fs built from: Ubuntu 20.04
> 
> When I asked Nvidia directly, their response was "Most likely it could
> be wifi driver issue because it gives."
> 

So you have to report upstream here, right?

> These are the drivers being loaded:
> 
> rt2800usb              36864  0
> rt2x00usb              24576  1 rt2800usb
> rt2800lib             122880  1 rt2800usb
> rt2x00lib              77824  3 rt2800usb,rt2x00usb,rt2800lib
> mac80211              811008  3 rt2x00lib,rt2x00usb,rt2800lib
> cfg80211              724992  2 rt2x00lib,mac80211
> 

I don't see rt2800usb module in the mainline kernel. Is it out-of-tree?
(no wonder why it taints your kernel)

> I've not worked with driver code before, so I am out of my element
> here.  I saw in the git history for rt2800usb some changes went in
> since I was using the USB wifi adapter on an older system that has a
> linux version older than 2019 (when the OS was compiled and flashed on
> the machine).
> 

Where is the repo?

Last but not least, please don't top-post; reply inline with appropriate
context instead.

Confused...

-- 
An old man doll... just what I always wanted! - Clara


  reply	other threads:[~2023-10-01  5:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEXpi5Rd6Y4umKOWRsCjX0kit=W5ZrVhn=MuRkyvJPwmjjDVnA@mail.gmail.com>
2023-10-01  5:12 ` Bagas Sanjaya
2023-10-01  5:33   ` enc0der
2023-10-01  5:53     ` Bagas Sanjaya [this message]
2023-10-03  5:47       ` Kalle Valo
2023-10-02 18:50   ` Stanislaw Gruszka
2023-10-03  0:01     ` Bagas Sanjaya
2023-10-04  1:34     ` enc0der
2023-10-04  4:44       ` Linux regression tracking (Thorsten Leemhuis)
2023-10-04 18:28       ` Stanislaw Gruszka
2023-10-05 18:08         ` enc0der

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3d246a72-2755-484f-8274-0c61fc185592@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=andre.przywara@arm.com \
    --cc=bjorn@mork.no \
    --cc=boqun.feng@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=enc0der@gmail.com \
    --cc=frederic@kernel.org \
    --cc=gaul@gaul.org \
    --cc=hayeswang@realtek.com \
    --cc=helmut.schaa@googlemail.com \
    --cc=horms@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=josh@joshtriplett.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=paulmck@kernel.org \
    --cc=qiang.zhang1211@gmail.com \
    --cc=quic_neeraju@quicinc.com \
    --cc=rcu@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=rostedt@goodmis.org \
    --cc=stf_xl@wp.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®