linux-kernel - Re: earlyprintk=xdbc seems broken

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <yt9dbl00rmgx.fsf@linux.ibm.com>
Date:   Tue, 25 Jan 2022 14:09:18 +0100
From:   Sven Schnelle <svens@...ux.ibm.com>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     Mathias Nyman <mathias.nyman@...ux.intel.com>,
        Greg KH <gregkh@...uxfoundation.org>,
        Dave Hansen <dave.hansen@...el.com>,
        Lu Baolu <baolu.lu@...ux.intel.com>, x86@...nel.org,
        linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
        Chunfeng Yun <chunfeng.yun@...iatek.com>
Subject: Re: earlyprintk=xdbc seems broken

Peter Zijlstra <peterz@...radead.org> writes:

> Now the documentation states we need this super speed A<->A cable, but
> could you also update the documentation for usb-c ? There's a fair
> number of usb-c only devices out there now.

Stupid beginners question: Would every USB3 A-A cable work, or are the
debug cables special? I've read the RX/TX pairs have to be swapped, but
to me it looks like that's always the case?

I'm just asking because i tried to debug a before-framebuffer crash on
my Thinkpad X1, but didn't have any luck getting xdbc running. Maybe
because of the bug above. Would be nice if someone could confirm whether
that should work with every USB3 A-A cable.

Thanks,
Sven