[Bug 206427] New: go7007 driver fails to handle interrupt

[Bug 206427] New: go7007 driver fails to handle interrupt

[bugzilla-daemon]

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!

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

Re: [Bug 206427] New: go7007 driver fails to handle interrupt

[Greg KH]

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

[Bug 206427] go7007 driver fails to handle interrupt

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=206427

--- Comment #1 from Greg Kroah-Hartman (greg@kroah.com) ---
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

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 206427] go7007 driver fails to handle interrupt

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=206427

--- Comment #3 from Takashi Iwai (tiwai@suse.de) ---
FWIW, 5.5.y kernel is found in OBS Kernel:stable and Kernel:HEAD repos (both
are equivalent at this moment).

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 206427] go7007 driver fails to handle interrupt

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=206427

--- Comment #4 from Josef Möllers (josef.moellers@suse.com) ---
Thanks. I'm just waiting for the build to finish, it's writing out the RPMs.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 206427] go7007 driver fails to handle interrupt

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=206427

--- Comment #5 from Josef Möllers (josef.moellers@suse.com) ---
(In reply to Greg Kroah-Hartman from comment #1)

> And can you try the 5.5 kernel, 5.3.y is old and obsolete.


It took a while, but: Yes, the problem still exists in 5.5.1!

I'll atache the relevant part of the messages file.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 206427] go7007 driver fails to handle interrupt

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=206427

--- Comment #7 from Takashi Iwai (tiwai@suse.de) ---
Could you give lsusb -v output of this device, too?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 206427] go7007 driver fails to handle interrupt

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=206427

--- Comment #8 from Takashi Iwai (tiwai@suse.de) ---
Also please give the whole dmesg output from the boot.  hwinfo output would be
helpful, too.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 206427] go7007 driver fails to handle interrupt

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=206427

--- Comment #9 from Josef Möllers (josef.moellers@suse.com) ---
Created attachment 287159
  --> https://bugzilla.kernel.org/attachment.cgi?id=287159&action=edit
lsusb -v output of device, dmesg and hwinfo

This is slightly different from what I remember:
In Ye Olde Days, the device would present itself as 093b:a002 and (through a
udev rule), a script would be run which downloaded the firmware (through
/sbin/fxload some hex file) to the device which would then disconnect and
reconnect as 093b:a102.

Now I see in the journal that this is now handled by go7007-loader.ko loading
/lib/firmware/go7007/px-m402u.fw!

Anyways ... infos attached.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 206427] go7007 driver fails to handle interrupt

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=206427

--- Comment #10 from Takashi Iwai (tiwai@suse.de) ---
Yes, the firmware loading mechanism went to the kernel module.

The kernel warning seems fixed by correcting the urb properly like the patch
below.  I'll submit to upstream.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 206427] go7007 driver fails to handle interrupt

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=206427

--- Comment #11 from Takashi Iwai (tiwai@suse.de) ---
Created attachment 287177
  --> https://bugzilla.kernel.org/attachment.cgi?id=287177&action=edit
Fix patch

-- 
You are receiving this mail because:
You are watching the assignee of the bug.