From: Randy Dunlap <rdunlap@infradead.org>
To: Alan Stern <stern@rowland.harvard.edu>,
Greg KH <gregkh@linuxfoundation.org>
Cc: ariel marcovitch <arielmarcovitch@gmail.com>,
johan@kernel.org, linux-usb@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Gaps in logs while using usb-serial as a console
Date: Mon, 30 Oct 2023 20:51:06 -0700 [thread overview]
Message-ID: <842a0d64-279d-4052-a243-95fee608ea76@infradead.org> (raw)
In-Reply-To: <968c62ca-0ef2-4bf1-a17b-a6d88d5e2e20@rowland.harvard.edu>
On 10/30/23 07:19, Alan Stern wrote:
> On Mon, Oct 30, 2023 at 09:30:15AM +0100, Greg KH wrote:
>> On Mon, Oct 30, 2023 at 10:15:30AM +0200, ariel marcovitch wrote:
>>>> Please realize that usb-serial console was the result of me loosing a
>>>> drunken bet. It's amazing it works at all. For "fake" devices like
>>> LOL your drunken bet was quite helpful to some people
>>> Because modern PCs come without a serial port, I wanted to use it to
>>> see early logs on my crashing kernel without having to use printk
>>> delay and things like that.
>>> I'm curious as to how kernel people debug PCs in general...
>>
>> We use a usb debug port connection (it's a special cable).
For EHCI it is a special cable. For XHCI you can use a special cable but
it is not required. (I saw a few people on LKML say that a normal data cable
works so I tested it and it does work.)
But if you want the special cable (for XHCI), this one works:
https://www.datapro.net/products/usb-3-0-super-speed-a-a-debugging-cable.html
So I tested with both the special debug cable and a normal A-A data cable,
both with satisfactory results.
> Sometimes people use netconsole (see
> Documentation/networking/netconsole.rst). I don't know how common it is
> nowadays, and it may not be quite as reliable as a debug port device,
> but it should still work. And it doesn't require special hardware.
It would be great if netconsole worked with wifi and not wired (ethernet).
--
~Randy
next prev parent reply other threads:[~2023-10-31 3:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 18:21 Gaps in logs while using usb-serial as a console ariel marcovitch
2023-10-30 6:22 ` Greg KH
2023-10-30 8:15 ` ariel marcovitch
2023-10-30 8:30 ` Greg KH
2023-10-30 14:19 ` Alan Stern
2023-10-31 3:51 ` Randy Dunlap [this message]
2023-11-09 18:55 ` ariel marcovitch
2023-11-10 8:38 ` Greg KH
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=842a0d64-279d-4052-a243-95fee608ea76@infradead.org \
--to=rdunlap@infradead.org \
--cc=arielmarcovitch@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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