From: David Gow <david@davidgow.net>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Harald Arnesen <linux@skogtun.org>,
Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: Danilo Krummrich <dakr@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BISECTED]: Black screen on 7.0-rc1
Date: Thu, 26 Feb 2026 12:08:24 +0800 [thread overview]
Message-ID: <67f655bb-4d81-4609-b008-68d200255dd2@davidgow.net> (raw)
In-Reply-To: <CAHk-=wgUmxkjwsWzX1rTo=DTnaouwY-VT8BjrTqfH7RmTwO72w@mail.gmail.com>
Le 25/02/2026 à 12:57 AM, Linus Torvalds a écrit :
> On Mon, 23 Feb 2026 at 23:59, Harald Arnesen <linux@skogtun.org> wrote:
>>
>>>>> In fact, I would expect it to be related to one (or both) of
>>>>>
>>>>> f2ae92780ab9 ("firewire: ohci: split page allocation from dma mapping")
>>>>> 993ab48006b3 ("firewire: ohci: stop using page private to store
>>>>> DMA mapping address")
>>>>
>>>> Should I try reverting one or both of these?
>>>
>>> Yes. From a quick check, they revert cleanly (revert 993ab48006b3
>>> first) and the result seems to compile cleanly too.
>>
>> I can confirm that the kernel boots with these two reverted.
>> I have attached the new dmesg output.
>
> Thanks. I guess it's up to Takashi to figure out what exactly goes
> wrong, but it's good to have this confirmed. I hope you'll be willing
> to test any patches that Takashi comes up with.
>
> And if we can't figure it out, I guess reverting them is the right
> thing, but let's wait until at least rc2 is imminent before we do
> that.
>
I am also seeing this, and can confirm that reverting the whole firewire
pull fixes it here.
Interestingly, I was seeing the same firewire_ohci/vmap errors during
the bisection (with those firewire patches included), but it was only
the merge which actually caused the system to not boot (again, with udev
seeming to hang).
Feel free to send any patches my way to test.
-- David
next prev parent reply other threads:[~2026-02-26 4:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18b0ead7-0a5d-4699-a09d-de5bc2208b68@skogtun.org>
2026-02-23 11:36 ` Harald Arnesen
[not found] ` <CAHk-=whsxHKbtSpiqqQ1V8YDh_zu+CMB=Zt9MxUOmWGocueZNQ@mail.gmail.com>
2026-02-23 21:29 ` Harald Arnesen
2026-02-24 0:25 ` Linus Torvalds
2026-02-24 7:59 ` Harald Arnesen
2026-02-24 16:57 ` Linus Torvalds
2026-02-25 10:23 ` Luna Jernberg
2026-02-26 4:08 ` David Gow [this message]
2026-02-28 7:22 ` Thorsten Leemhuis
2026-02-28 9:10 ` David Gow
2026-02-28 9:58 ` Harald Arnesen
2026-02-28 18:09 ` Linus Torvalds
2026-02-28 21:43 ` Harald Arnesen
2026-02-27 16:01 ` Harald Arnesen
[not found] ` <f86acb3e-654e-4be6-ad05-af62e4c185a3@skogtun.org>
2026-02-24 16:46 ` Harald Arnesen
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=67f655bb-4d81-4609-b008-68d200255dd2@davidgow.net \
--to=david@davidgow.net \
--cc=dakr@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@skogtun.org \
--cc=o-takashi@sakamocchi.jp \
--cc=torvalds@linux-foundation.org \
/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®