From: Peter Zijlstra <peterz@infradead.org>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Dave Hansen <dave.hansen@intel.com>,
Lu Baolu <baolu.lu@linux.intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org,
Chunfeng Yun <chunfeng.yun@mediatek.com>
Subject: Re: earlyprintk=xdbc seems broken
Date: Tue, 25 Jan 2022 11:54:06 +0100 [thread overview]
Message-ID: <Ye/Wzte0qr/LVLfL@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <Ye/VL4b1PUCsCeds@hirez.programming.kicks-ass.net>
On Tue, Jan 25, 2022 at 11:47:11AM +0100, Peter Zijlstra wrote:
> On Tue, Jan 25, 2022 at 10:51:00AM +0200, Mathias Nyman wrote:
> > On 24.1.2022 18.46, Peter Zijlstra wrote:
>
> > > FYI, I'm thinking early_xdbc_parse_parameter should've now given
> > > dpgp_num: 1 ?
> > >
> >
> > Yes, it should.
> >
> > Looks like there's a parsing issue.
> > "earlyprintk=xdbc1,keep" fails on our Tigerlake as well.
> >
> > Without the "keep" option it works for me:
> >
> > [ 0.000000] Command line: console=ttyS0,115200n8 buildroot_hostname=tgl04 earlyprintk=xdbc1 dmi_entry_point=0x74374000
> > [ 0.000000] xhci_dbc:early_xdbc_parse_parameter: dbgp_num: 1
>
> [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.16.0+ root=UUID=a652986c-fbc6-4341-85c3-b4ad4402f130 ro debug ignore_loglevel sysrq_always_enabled usbcore.autosuspend=-1 earlyprintk=xdbc1,keep force_early_printk sched_verbose ft
> race=nop mitigations=off nokaslr
>
> [ 0.000000] xhci_dbc:early_xdbc_parse_parameter: dbgp_num: 1
>
> [ 0.399988] xhci_dbc:xdbc_start: DbC is running now, control 0x8d000003 port ID 15
> [ 0.399998] xhci_dbc:xdbc_handle_port_status: connect status change event
> [ 0.399999] xhci_dbc:xdbc_handle_port_status: port reset change event
> [ 0.431217] printk: console [earlyxdbc0] enabled
>
> Success!! I'll go submit proper patches for this then.
Next up, I don't suppose there's working patches for GRUB ? Because the
moment the thing gets stuck on a non-working kernel I'm screwed again :/
next prev parent reply other threads:[~2022-01-25 10:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 15:22 earlyprintk=xdbc seems broken Peter Zijlstra
2021-12-03 0:52 ` Lu Baolu
2021-12-03 14:31 ` Mathias Nyman
2021-12-03 15:22 ` Dave Hansen
2021-12-03 15:29 ` Greg KH
2021-12-17 11:01 ` Mathias Nyman
2021-12-17 13:55 ` Peter Zijlstra
2021-12-17 15:19 ` Greg KH
2021-12-20 14:40 ` Peter Zijlstra
2021-12-20 15:06 ` Greg KH
2021-12-20 17:01 ` Peter Zijlstra
2021-12-20 14:34 ` Mathias Nyman
2021-12-20 15:51 ` Peter Zijlstra
2021-12-21 9:40 ` Peter Zijlstra
2021-12-21 9:41 ` Peter Zijlstra
2022-01-14 8:47 ` Peter Zijlstra
2022-01-14 19:31 ` Mathias Nyman
2022-01-15 16:06 ` Peter Zijlstra
2022-01-24 14:55 ` Mathias Nyman
2022-01-24 16:39 ` Peter Zijlstra
2022-01-24 16:46 ` Peter Zijlstra
2022-01-25 8:51 ` Mathias Nyman
2022-01-25 10:47 ` Peter Zijlstra
2022-01-25 10:54 ` Peter Zijlstra [this message]
2022-01-25 12:45 ` Peter Zijlstra
2022-01-25 13:09 ` Sven Schnelle
2022-01-25 13:54 ` Peter Zijlstra
2022-01-25 14:01 ` Sven Schnelle
2022-01-25 17:13 ` Mathias Nyman
2022-01-25 16:24 ` Dave Hansen
2022-02-17 3:44 ` Randy Dunlap
2022-01-25 19:39 ` Rajaram R
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=Ye/Wzte0qr/LVLfL@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=baolu.lu@linux.intel.com \
--cc=chunfeng.yun@mediatek.com \
--cc=dave.hansen@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.