From: Greg KH <greg@kroah.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-usb@vger.kernel.org
Subject: Re: [Bug 206427] New: go7007 driver fails to handle interrupt
Date: Wed, 5 Feb 2020 12:29:21 +0000 [thread overview]
Message-ID: <20200205122921.GA1186249@kroah.com> (raw)
In-Reply-To: <bug-206427-208809@https.bugzilla.kernel.org/>
On Wed, Feb 05, 2020 at 12:24:50PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=206427
>
> Bug ID: 206427
> Summary: go7007 driver fails to handle interrupt
> Product: Drivers
> Version: 2.5
> Kernel Version: 5.3.18
> Hardware: x86-64
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: USB
> Assignee: drivers_usb@kernel-bugs.kernel.org
> Reporter: josef.moellers@suse.com
> Regression: No
>
> Created attachment 287141
> --> https://bugzilla.kernel.org/attachment.cgi?id=287141&action=edit
> Kernel trace shown when error is reported.
>
> When connecting a Plextor ConvertX M402U video converter, a "BOGUS urb xfer" is
> reported and a Call Trace is dumped.
> I assume that the go7007 driver has not been fully supported in newer kernel
> versions as it definitely used to work in 2.x kernels!
Can you provide the full kernel log message here please?
And can you try the 5.5 kernel, 5.3.y is old and obsolete.
thanks,
greg k-h
next prev parent reply other threads:[~2020-02-05 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 12:24 [Bug 206427] New: go7007 driver fails to handle interrupt bugzilla-daemon
2020-02-05 12:29 ` Greg KH [this message]
2020-02-05 12:29 ` [Bug 206427] " bugzilla-daemon
2020-02-05 13:45 ` bugzilla-daemon
2020-02-05 13:57 ` bugzilla-daemon
2020-02-05 15:43 ` bugzilla-daemon
2020-02-06 9:27 ` bugzilla-daemon
2020-02-06 9:33 ` bugzilla-daemon
2020-02-06 10:00 ` bugzilla-daemon
2020-02-06 15:34 ` bugzilla-daemon
2020-02-06 15:43 ` bugzilla-daemon
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=20200205122921.GA1186249@kroah.com \
--to=greg@kroah.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@vger.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 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).