linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: "StarostaCZ@gmail.com" <starostacz@gmail.com>,
	Joerg Roedel <joro@8bytes.org>, Johan Hovold <johan@kernel.org>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	iommu@lists.linux-foundation.org, linux-usb@vger.kernel.org
Subject: Re: Linux crash when using FTDI FT232R USB to serial converter on AMD boards.
Date: Thu, 16 May 2019 10:34:52 +0200	[thread overview]
Message-ID: <1557995692.14649.2.camel@suse.com> (raw)
In-Reply-To: <b4c3eba7-758d-7951-afd0-d90a261346e8@gmail.com>

On Do, 2019-05-16 at 10:20 +0200,  StarostaCZ@gmail.com  wrote:
> Dne 16.5.2019 v 9:58 Oliver Neukum napsal(a):
> > > > 2.Send a new report to the corresponding mailing list
> > > 
> > > Which mailing list is correct?
> > 
> > In that case linux-usb@vger.kernel.org
> > 
> > 	HTH
> > 		Oliver
> > 
> 
> Is there some rules how to send bug report? Or I can send report with 
> "my amateur description"?

Mention

1. kernel version
2. whether this is known to be a regression
3. include the log with iommu disabled and mention that you disabled
the IOMMU
4. Include the output of lsusb

	HTH
		Oliver


  reply	other threads:[~2019-05-16  8:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26 13:47 Linux crash when using FTDI FT232R USB to serial converter on AMD boards StarostaCZ@gmail.com
2019-04-29  9:48 ` Johan Hovold
2019-04-29 10:51   ` StarostaCZ@gmail.com
2019-04-29 11:22     ` Johan Hovold
2019-04-29 11:48       ` StarostaCZ@gmail.com
2019-05-03 15:37   ` Joerg Roedel
2019-05-06  7:10     ` StarostaCZ@gmail.com
2019-05-15  7:54       ` StarostaCZ@gmail.com
2019-05-15  9:17         ` Oliver Neukum
2019-05-15  9:43           ` StarostaCZ@gmail.com
     [not found]           ` <3e7ec2f2-ac47-a031-96ba-fa2b9f21ed2e@gmail.com>
     [not found]             ` <1557913582.2950.15.camel@suse.com>
2019-05-15 11:22               ` StarostaCZ@gmail.com
     [not found]               ` <c57ccafd-7ad4-63e4-54c1-e1fb136ebeed@gmail.com>
     [not found]                 ` <1557928483.2950.18.camel@suse.com>
2019-05-15 14:15                   ` StarostaCZ@gmail.com
2019-05-16  7:58                     ` Oliver Neukum
2019-05-16  8:20                       ` StarostaCZ@gmail.com
2019-05-16  8:34                         ` Oliver Neukum [this message]
2019-05-16 12:29                           ` StarostaCZ@gmail.com
2019-05-16 13:11                             ` Oliver Neukum
2019-05-16 13:36                               ` StarostaCZ@gmail.com

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=1557995692.14649.2.camel@suse.com \
    --to=oneukum@suse.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=johan@kernel.org \
    --cc=joro@8bytes.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=starostacz@gmail.com \
    /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).