Re: Odroid C4: dwc2_hsotg_start_req: ep1 is stalled

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, May 20, 2021 at 05:18:37PM +0300, Matwey V. Kornilov wrote:
> чт, 20 мая 2021 г. в 17:16, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>:
> >
> > On Thu, May 20, 2021 at 03:35:26PM +0300, Matwey V. Kornilov wrote:
> > > Hi,
> > >
> > > I am running upstream Linux 5.12.3 on an Odroid C4 board and see lots
> > > of the following lines in dmesg while using the gadget mass storage
> > > driver. I suppose that this can indicate some issue in the dwc2
> > > driver.
> > >
> > > [  189.752586] dwc2 ff400000.usb: bound driver g_mass_storage
> > > [  190.118994] dwc2 ff400000.usb: new device is high-speed
> > > [  190.199074] dwc2 ff400000.usb: new device is high-speed
> > > [  190.267855] dwc2 ff400000.usb: new address 4
> > > [  191.310603] dwc2 ff400000.usb: dwc2_hsotg_ep_sethalt(ep
> > > 00000000ce48180a ep1in, 1)
> > > [  191.310737] dwc2 ff400000.usb: dwc2_hsotg_start_req: ep1 is stalled
> > > [  191.311015] dwc2 ff400000.usb: dwc2_hsotg_ep_sethalt(ep
> > > 00000000ce48180a ep1in, 0)
> > > [  191.312257] dwc2 ff400000.usb: dwc2_hsotg_ep_sethalt(ep
> > > 00000000ce48180a ep1in, 1)
> > > [  191.312373] dwc2 ff400000.usb: dwc2_hsotg_start_req: ep1 is stalled
> > > [  191.312762] dwc2 ff400000.usb: dwc2_hsotg_ep_sethalt(ep
> > > 00000000ce48180a ep1in, 0)
> > > [  191.336959] dwc2 ff400000.usb: dwc2_hsotg_ep_sethalt(ep
> > > 00000000ce48180a ep1in, 1)
> > > [  191.447759] dwc2 ff400000.usb: dwc2_hsotg_ep_sethalt(ep
> > > 00000000ce48180a ep1in, 1)
> > > [  191.447823] dwc2 ff400000.usb: dwc2_hsotg_start_req: ep1 is stalled
> > > [  191.448098] dwc2 ff400000.usb: dwc2_hsotg_ep_sethalt(ep
> > > 00000000ce48180a ep1in, 0)
> > > [  191.448550] dwc2 ff400000.usb: dwc2_hsotg_ep_sethalt(ep
> > > 00000000ce48180a ep1in, 1)
> > > [  191.567748] dwc2 ff400000.usb: dwc2_hsotg_ep_sethalt(ep
> > > 00000000ce48180a ep1in, 1)
> >
> > Those look like they ought to be debugging messages.  They don't seem to
> > indicate any problem.
> >
> > Alan Stern
> 
> Well, I have not enabled any debug info, and those messages are
> flooding my dmesg. Maybe dev_warn() should be replaced with something
> other?

Indeed, maybe it should.  Feel free to go ahead and submit a patch.

Alan Stern



[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux