mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Gow <david@davidgow.net>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
	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>,
	Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [BISECTED]: Black screen on 7.0-rc1
Date: Sat, 28 Feb 2026 17:10:15 +0800	[thread overview]
Message-ID: <a8277e96-6718-4e32-b46b-41738e55d80e@davidgow.net> (raw)
In-Reply-To: <f347b759-c3c6-40fe-86b2-b89ac6fd2d5b@leemhuis.info>

Le 28/02/2026 à 3:22 PM, Thorsten Leemhuis a écrit :
> On 2/26/26 05:08, David Gow wrote:
>> 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
>>>>>>>        993ab48006b3 ("firewire: ohci: stop using page private to store >>>>>> dma mapping")
>>>>>> 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.
> 
> TWIMC, John ran into a problem with mentioned f2ae92780ab9 commit that
> from a brief look looks similar to the one Harald reported. And Takashi
> posted a fix for it here:
> https://lore.kernel.org/lkml/20260228031255.GA832746@workstation.local/
> 
> Not sure why Takashi did not reply here. Feels a bit like I'm missing
> something.
> 

Thanks, that patch indeed fixes it for me, too.

-- David

  reply	other threads:[~2026-02-28  9:10 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
2026-02-28  7:22             ` Thorsten Leemhuis
2026-02-28  9:10               ` David Gow [this message]
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=a8277e96-6718-4e32-b46b-41738e55d80e@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=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --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®