linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Johan Hovold <johan@kernel.org>,
	primalmotion <primalmotion@pm.me>
Cc: 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: Fri, 22 Sep 2023 14:18:18 +0700	[thread overview]
Message-ID: <ZQ0_upwsFTIduIRQ@debian.me> (raw)
In-Reply-To: <5eb57bfe-94a4-136b-497e-deeb31846db1@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]

On Fri, Jul 07, 2023 at 07:10:13AM +0700, Bagas Sanjaya 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).
> 
> 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
> 

A PureBoot developer noted that this regression is firmware bug
(see Bugzilla), thus:

#regzbot inconclusive: firmware bug, fixing the kernel only workarounds buggy firmware

Thanks.


-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      parent reply	other threads:[~2023-09-22  7:27 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
2023-09-22  7:18 ` Bagas Sanjaya [this message]

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=ZQ0_upwsFTIduIRQ@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.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).