From: Randy Dunlap <rdunlap@infradead.org>
To: "Dr. David Alan Gilbert" <linux@treblig.org>,
Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Johan Hovold <johan@kernel.org>,
primalmotion <primalmotion@pm.me>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux USB <linux-usb@vger.kernel.org>
Subject: Re: Fwd: unable to boot when monitor is attached
Date: Thu, 6 Jul 2023 18:48:48 -0700 [thread overview]
Message-ID: <9e770151-698c-0efe-8ea2-495f1ae54931@infradead.org> (raw)
In-Reply-To: <ZKdgMs2ChLnJ3U8n@gallifrey>
On 7/6/23 17:45, Dr. David Alan Gilbert wrote:
> * Bagas Sanjaya (bagasdotme@gmail.com) wrote:
>> Hi,
>>
>> I notice a regression report on Bugzilla [1]. Quoting from it:
>>
>>>
>>> In the latest 6.3 and 6.4, it is impossible for me to boot my laptop if my DELL U2720Q monitor is plugged in (USB-C). I have to unplug it, then boot. As soon as the first second of boot went through, I can plug in my monitor and there is no issue afterward. There is no issue waking up after suspend. Only when it boots.
>>>
>>> See the attached pictures of the trace. The trace itself seems random (at least to me :)). I tried several things, like removing any attached USB devices from the monitor built-in USB-hub, but that does not change anything. (there is a keyboard and trackpad attached).
>>
>> See Bugzilla for the full thread.
>>
>> Unfortunately, the reporter can only provide photos of kernel trace
>> (as he doesn't have any other means to extract kernel logs, maybe
>> connecting over serial helps; see Bugzilla for these attachments).
>
> I note the photos have 'crud' at the bottom; as if something interesting
> is in the video ram; perhaps something is freaked out by this nice 4k
> monitor and some useful data structures are ending up in video ram.
>
> (Also note it's a librem with pureboot)
>
> Dave
>
>>
>> Anyway, I'm adding it to regzbot so that it doesn't fall through
>> cracks unnoticed:
>>
>> #regzbot introduced: v6.1..v6.3 https://bugzilla.kernel.org/show_bug.cgi?id=217637
>> #regzbot title: unable to boot with Dell U2720Q monitor attached
>>
>> Thanks.
>>
>> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=217637
So what are __pfx_worker_thread and __pfx_kthread?
Where are they from?
--
~Randy
next prev parent reply other threads:[~2023-07-07 1:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 0:10 Fwd: unable to boot when monitor is attached Bagas Sanjaya
2023-07-07 0:45 ` Dr. David Alan Gilbert
2023-07-07 1:48 ` Randy Dunlap [this message]
2023-09-22 7:18 ` Bagas Sanjaya
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=9e770151-698c-0efe-8ea2-495f1ae54931@infradead.org \
--to=rdunlap@infradead.org \
--cc=bagasdotme@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@treblig.org \
--cc=primalmotion@pm.me \
/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).