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, 26 Jun 2023 16:33:04 -0500 [thread overview]
Message-ID: <RO2P215MB193898F3008E0F390CCEBC87A726A@RO2P215MB1938.LAMP215.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <6afa0ebc-1d3f-8cba-79dc-8ddfe13c296a@lwfinger.net>
On 6/26/23 10:21 AM, Larry Finger wrote:
> On 6/26/23 07:44, Sardonimous wrote:
>> If I were to send you some test patches, could you create a kernel
>> with them applied?
>>
>> Doubtful.
>
> Sardonimous,
>
> OK, that essentially eliminates getting DMA to work. The cost of a
> MacBookPro7 is too much for me to acquire one to debug that issue.
>
> On my PowerBook G4, I also got the failure to connect, thus I should
> be able to fix that problem, but getting a new kernel with the fix
> onto your machine will not be easy.
It might be possible to follow the arch instructions for patching the kernel
https://wiki.archlinux.org/title/Kernel/Arch_build_system
It takes about a day to rebuild the kernel following this procedure.
> Is it possible to ssh into your machine, or to use TeamViewer? Those
> questions do not need an answer now, but think about them.
This is complicated by being in a CGNAT environment. I usually do this
via tailscale. Will have to think about it.
> Larry
Should pio=1 qos=0 cause the problems that it does? It if is no longer
a supported configuration, perhaps it should fail more gracefully.
next prev parent reply other threads:[~2023-06-26 21:33 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 [this message]
2023-06-27 0:31 ` Larry Finger
2023-07-03 17:35 ` Larry Finger
2023-07-03 20:13 ` Sardonimous
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=RO2P215MB193898F3008E0F390CCEBC87A726A@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).