From: Mike Lothian <mike@fireburn.co.uk>
To: Ben Greear <greearb@candelatech.com>
Cc: khalid@gonehiking.org, Deren.Wu@mediatek.com,
Eddie.Chen@mediatek.com, Eric-SY.Chang@mediatek.com,
Eric.Liang@mediatek.com, Leon.Yen@mediatek.com,
Mark-YW.Chen@mediatek.com, Soul.Huang@mediatek.com,
Stella.Chang@mediatek.com, Tom.Chou@mediatek.com,
YN.Chen@mediatek.com, abhishekpandit@google.com,
ch.yeh@mediatek.com, frankgor@google.com, jemele@google.com,
jenhao.yang@mediatek.com, jsiuda@google.com, km.lin@mediatek.com,
linux-mediatek@lists.infradead.org,
linux-wireless@vger.kernel.org, lorenzo.bianconi@redhat.com,
nbd@nbd.name, posh.sun@mediatek.com, robin.chiu@mediatek.com,
sean.wang@mediatek.com, shawnku@google.com,
steve.lee@mediatek.com, ted.huang@mediatek.com
Subject: Re: [PATCH] mt76: mt7921e: fix possible probe failure after reboot
Date: Tue, 25 Jan 2022 22:56:10 +0000 [thread overview]
Message-ID: <CAHbf0-FwH-ftCFeqrNusu4DBPrKe0SeTAQnAZngpsn+At-fJsQ@mail.gmail.com> (raw)
In-Reply-To: <9d692dc9-4b24-44b0-cbe0-dfc33f3d5f03@candelatech.com>
On Tue, 25 Jan 2022 at 18:09, Ben Greear <greearb@candelatech.com> wrote:
>
> On 1/25/22 6:16 AM, Mike Lothian wrote:
> > On Thu, 20 Jan 2022 at 09:56, Mike Lothian <mike@fireburn.co.uk> wrote:
> >>
> >> Hi
> >>
> >> I get a BUG and the kernel resuses to boot with this patch when mt76 is compiled into the kernel
> >>
> >> https://bugzilla.kernel.org/show_bug.cgi?id=214557
> >>
> >> I don't see this issue when mt76 is compiled as a module
> >>
> >> My .config is at https://github.com/FireBurn/KernelStuff/blob/master/dot_config_tip
> >>
> >> Let me know if you'd like any more info
> >>
> >> Cheers
> >>
> >> Mike
> >
> > The bug I was hitting was due to a different change introduced in rc1,
> > with that reverted your patches work great
>
> What patch did you revert?
>
> Thanks,
> Ben
>
Hi
I reverted both 730b49aac426e1e8016d3c2dd6b407e500423821 and
510a0bdb2bfcff8d7be822c72adc3add7a97d559
But there's a fix now,
https://patchwork.kernel.org/project/linux-usb/patch/20220124090228.41396-2-heikki.krogerus@linux.intel.com/
I'm able to load mt76 as a module or built in
Cheers
Mike
next prev parent reply other threads:[~2022-01-25 22:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 7:30 [PATCH] mt76: mt7921e: fix possible probe failure after reboot sean.wang
2022-01-18 18:16 ` Khalid Aziz
2022-01-20 9:56 ` Mike Lothian
2022-01-25 14:16 ` Mike Lothian
2022-01-25 18:09 ` Ben Greear
2022-01-25 22:56 ` Mike Lothian [this message]
2022-02-24 16:54 ` Mike Lothian
2022-01-21 6:33 ` Janusz Dziedzic
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=CAHbf0-FwH-ftCFeqrNusu4DBPrKe0SeTAQnAZngpsn+At-fJsQ@mail.gmail.com \
--to=mike@fireburn.co.uk \
--cc=Deren.Wu@mediatek.com \
--cc=Eddie.Chen@mediatek.com \
--cc=Eric-SY.Chang@mediatek.com \
--cc=Eric.Liang@mediatek.com \
--cc=Leon.Yen@mediatek.com \
--cc=Mark-YW.Chen@mediatek.com \
--cc=Soul.Huang@mediatek.com \
--cc=Stella.Chang@mediatek.com \
--cc=Tom.Chou@mediatek.com \
--cc=YN.Chen@mediatek.com \
--cc=abhishekpandit@google.com \
--cc=ch.yeh@mediatek.com \
--cc=frankgor@google.com \
--cc=greearb@candelatech.com \
--cc=jemele@google.com \
--cc=jenhao.yang@mediatek.com \
--cc=jsiuda@google.com \
--cc=khalid@gonehiking.org \
--cc=km.lin@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=nbd@nbd.name \
--cc=posh.sun@mediatek.com \
--cc=robin.chiu@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shawnku@google.com \
--cc=steve.lee@mediatek.com \
--cc=ted.huang@mediatek.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).