From: Sardonimous <sardonimous@hotmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>,
Arnd Bergmann <arnd@arndb.de>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux Wireless <linux-wireless@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>
Cc: "Michael Büsch" <m@bues.ch>, "kernel test robot" <lkp@intel.com>,
"Simon Horman" <simon.horman@corigine.com>,
"Kalle Valo" <kvalo@kernel.org>
Subject: Re: Fwd: After kernel 6.3.7 or 6.3.8 b43 driver fails
Date: Mon, 3 Jul 2023 15:13:38 -0500 [thread overview]
Message-ID: <RO2P215MB19383189863E11A1B242E02BA729A@RO2P215MB1938.LAMP215.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <89429625-5b5a-d0d3-ae82-0b7204262980@lwfinger.net>
On 7/3/23 12:35 PM, Larry Finger wrote:
> Sorry that it took so long to get back to you.
>
> For my ppc32, there is no regression. It took a while to learn the
> pio=1 and qos=0 are BOTH needed. That I do not understand, but with
> both set, the device works with kernel 6.4 and all earlier kernels
> that I tried. Fortunately, I did not need to do the entire bisection.
>
> I am working on eliminating the warning that appears with qos=0, but
> it does not inhibit operations.
>
> @Bagas Sanjaya: Please mark this "regression" as invalid.
>
> Larry
>
I appreciate the time you've spent on this. I did try 6.4 again (6.4.1
actually) and wlan0 did eventually come active. When I tried this
before, I probably got freaked by the number of WARNINGs when it wasn't
connecting, but perhaps it was failing for some other reason. I didn't
realize they were only warnings.
$ uptime
15:10:52 up 9 min, 3 users, load average: 0.11, 0.92, 0.85
$ journalctl --boot | grep "WARNING.*__ieee80211_stop_queue+0xcc/0xe0"
| wc -l
111
Regards.
next prev parent reply other threads:[~2023-07-03 20:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 1:44 Fwd: After kernel 6.3.7 or 6.3.8 b43 driver fails Bagas Sanjaya
2023-06-24 8:50 ` Michael Büsch
2023-06-24 9:29 ` Arnd Bergmann
2023-06-24 14:00 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-24 16:22 ` Larry Finger
2023-06-24 21:32 ` Fwd: " Arnd Bergmann
[not found] ` <RO2P215MB193850DDADD38492BEC8CC2FA720A@RO2P215MB1938.LAMP215.PROD.OUTLOOK.COM>
2023-06-25 0:50 ` Bagas Sanjaya
2023-06-25 2:09 ` Larry Finger
2023-06-25 4:41 ` Larry Finger
2023-06-25 16:58 ` Sardonimous
2023-06-25 18:12 ` Arnd Bergmann
2023-06-25 18:17 ` Larry Finger
2023-06-25 21:11 ` Sardonimous
2023-06-25 23:05 ` Larry Finger
2023-06-26 12:44 ` Sardonimous
2023-06-26 15:21 ` Larry Finger
2023-06-26 21:33 ` Sardonimous
2023-06-27 0:31 ` Larry Finger
2023-07-03 17:35 ` Larry Finger
2023-07-03 20:13 ` Sardonimous [this message]
2023-07-04 8:30 ` Linux regression tracking #update (Thorsten Leemhuis)
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=RO2P215MB19383189863E11A1B242E02BA729A@RO2P215MB1938.LAMP215.PROD.OUTLOOK.COM \
--to=sardonimous@hotmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=arnd@arndb.de \
--cc=bagasdotme@gmail.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.com \
--cc=m@bues.ch \
--cc=netdev@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=simon.horman@corigine.com \
/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;
as well as URLs for NNTP newsgroup(s).